Fense Proxy & VPN Blocker: A security weakness
Fense Proxy & VPN Blocker is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 3.0.1.
- Component
- Fense Proxy & VPN Blocker
- Plugin slug
fense-block-vpn-proxy- Affected
- <= 3.0.1
- Safe version
> 3.0.1- Published
- Jul 17, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jul 17, 2026 and is one of 1 known issue for this plugin.
Patch or disable the affected component.
Update Fense Proxy & VPN Blocker to a release after 3.0.1, or disable and remove it until a fixed version is available.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N