# CVE-2026-40784: WordPress FluentBoards plugin <= 1.91.2 - Insecure Direct Object References (IDOR) vulnerability

> Attackers can bypass access controls to read or modify data in the FluentBoards WordPress plugin via insecure direct object references.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 15 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-x75g-qm53-h84r

## What is CVE-2026-40784?

CVE-2026-40784 is a high-severity missing authorization vulnerability in Mahmudul Hasan Arif FluentBoards, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in Mahmudul Hasan Arif FluentBoards fluent-boards allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects FluentBoards: from n/a through <= 1.91.2.

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

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


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

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

## Is CVE-2026-40784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40784 is a high-severity missing authorization vulnerability in Mahmudul Hasan Arif FluentBoards, published on 15 Apr 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-40784 in the wild and no public exploit code.

Affected product: Mahmudul Hasan Arif FluentBoards. 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-40784/ (Markdown: https://insights.sbomify.com/CVE-2026-40784/index.md)
```

## Sources

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

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