# CVE-2026-81297: WordPress Fluent Forms Pro Add On Pack plugin <= 6.2.12 - Privilege Escalation vulnerability

> A privilege escalation vulnerability in the Fluent Forms Pro Add On Pack plugin allows subscribers to gain higher privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-5385-87qp-j5rg

## What is CVE-2026-81297?

CVE-2026-81297 is a high-severity vulnerability in WP Manage Ninja Fluent Forms Pro Add On Pack, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber Privilege Escalation in Fluent Forms Pro Add On Pack <= 6.2.12 versions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-81297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81297 is a high-severity vulnerability in WP Manage Ninja Fluent Forms Pro Add On Pack, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81297 in the wild and no public exploit code.

Affected product: WP Manage Ninja 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-81297/ (Markdown: https://insights.sbomify.com/CVE-2026-81297/index.md)
```

## Sources

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

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