# CVE-2026-94669: WordPress Fluent Forms Pro Add On Pack plugin <= 6.2.13 - Broken Access Control vulnerability

> Attackers can bypass access controls in the Fluent Forms Pro Add On Pack plugin to perform unauthorized actions.

- **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:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-wh3r-9jhx-wjrc

## What is CVE-2026-94669?

CVE-2026-94669 is a medium-severity missing authorization vulnerability in WP ManageNinja LLC Fluent Forms Pro Add On Pack, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in WP ManageNinja LLC Fluent Forms Pro Add On Pack fluentformpro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fluent Forms Pro Add On Pack: from n/a through 6.2.13.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94669 is a medium-severity missing authorization vulnerability in WP ManageNinja LLC Fluent Forms Pro Add On Pack, published on 5 Oct 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-94669 in the wild and no public exploit code.

Affected product: WP ManageNinja LLC Fluent Forms Pro Add On Pack. 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-94669/ (Markdown: https://insights.sbomify.com/CVE-2026-94669/index.md)
```

## Sources

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

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