# CVE-2026-78278: WordPress Fluent Boards Pro plugin <= 2.0.11 - Insecure Direct Object References (IDOR) vulnerability

> Subscribers can access or modify other users' data due to missing authorization checks in the Fluent Boards Pro plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** CVE-2026-78466, GHSA-qrr7-v4w9-q4hr

## What is CVE-2026-78278?

CVE-2026-78278 is a medium-severity missing authorization vulnerability in WP ManageNinja LLC Fluent Boards Pro, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Subscriber Insecure Direct Object References (IDOR) in Fluent Boards Pro <= 2.0.11 versions.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-78278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78278 is a medium-severity missing authorization vulnerability in WP ManageNinja LLC Fluent Boards Pro, published on 24 Aug 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-78278 in the wild and no public exploit code.

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

## Sources

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

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