Fense Proxy & Vpn Blocker
Approved changes feed: RSS · Atom
cpe:2.3:a:devozon:fense_proxy_&_vpn_blocker:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Devozon (75cd72d8-63bf-507a-a093-6ae74bc21d4d) |
|---|---|
| Product | Fense Proxy & Vpn Blocker (5bcfcd1c-ef80-5002-8dcb-c85ac2558ae8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-8616 |
vulnerable | 2026-07-29 01:09:06.036274 |
Fense Proxy & VPN Blocker <= 3.0.1 - Missing Authorization to Unauthenticated Plugin Option/Transient Deletion via fense_bpvt_save_settings AJAX Action
MEDIUM (5.3)
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.
Published: 2026-07-17T02:31:30.556Z
Updated: 2026-07-21T01:26:04.428Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.