mediumCVE-2026-8616

Fense Proxy & VPN Blocker <= 3.0.1 - Missing Authorization to Unauthenticated Plugin Option/Transient Deletion via fense_bpvt_save_settings AJAX Action

Q: What is affected by CVE-2026-8616?

Fense Proxy & VPN Blocker versions listed as affected should be reviewed: up to and including 3.0.1.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The Fense Proxy & VPN Blocker plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check and missing nonce validation on the fense_bpvt_save_settings() function in versions up to, and including, 3.0.1. The callback is registered to both wp_ajax_* and wp_ajax_nopriv_* hooks and unconditionally calls delete_option() on four plugin options and delete_transient() on three transients tied to the plugin's API key cache and settings. This makes it possible for unauthenticated attackers to delete plugin options and transients, effectively resetting the plugin's API key/data cache and forcing the plugin to refetch state.

Browse WordPress security risks

ProductFense Proxy & VPN Blocker

CVSS5.3

EPSS0.00228

UpdatedJuly 19, 2026

Quick answer

Fense Proxy & VPN Blocker should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

up to and including 3.0.1

Fixed versions

3.0.2

How to fix it

Fense Proxy & VPN Blocker is affected by CVE-2026-8616, a missing authorization flaw in its settings AJAX action. An unauthenticated attacker can delete plugin options and cache data, weakening the site's proxy and VPN controls. Update Fense Proxy & VPN Blocker to 3.0.2 or a newer vendor-supported patched release. Prioritize exposed production systems and accounts that can reach the affected feature.

Inventory every Fense Proxy & VPN Blocker deployment, version, exposed endpoint, environment, and owner.
Confirm the installed release is not an affected version up to and including 3.0.1.
Update Fense Proxy & VPN Blocker to 3.0.2 or a newer vendor-supported patched release.
Until the update is complete, disable Fense or block unauthenticated fense_bpvt_save_settings AJAX requests.
Review relevant logs and search for action=fense_bpvt_save_settings, reset options or transients, API cache misses, and gaps in blocking coverage.
Restore the approved plugin settings and API configuration, then review traffic that reached the site while protection was reduced.
Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm Fense Proxy & VPN Blocker is on the patched version or mitigation stated above and record the exact deployed version.
Confirm an unauthenticated caller cannot delete Fense options or transients and the expected blocking rules remain active.
Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-8616.

Related categories

WordPress Network Security API Security Authorization Bypass

Related security risks

More published guidance from the same primary category.

medium

Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret

Updated July 24, 2026

high

CVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

medium

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Updated July 24, 2026

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-8616?

Fense Proxy & VPN Blocker versions listed as affected should be reviewed: up to and including 3.0.1.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.