# CVE-2026-8616: Missing authorization in Fense Proxy & VPN Blocker

> Unauthenticated attackers can delete plugin options and transients, resetting the API key cache and forcing state refetching.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-56hc-jghx-566j

## What is CVE-2026-8616?

CVE-2026-8616 is a medium-severity missing authorization vulnerability in devozon Fense Proxy & VPN Blocker, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-8616?


## How do I fix CVE-2026-8616?

No fix has been published for CVE-2026-8616 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8616 being exploited?

There is no known exploitation of CVE-2026-8616 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8616 and fix it if it is affected.

What it is: CVE-2026-8616 is a medium-severity missing authorization vulnerability in devozon Fense Proxy & VPN Blocker, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8616 in the wild and no public exploit code.

Affected product: devozon Fense Proxy & VPN Blocker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8616/ (Markdown: https://insights.sbomify.com/CVE-2026-8616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8616
- OSV: https://osv.dev/vulnerability/CVE-2026-8616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8616/
Summaries are generated and may contain mistakes; the official description above is the record.