FluentBoards – Project Management, Task Management, Goal Tracking, Kanban Board, and, Team Collaboration <= 1.91.2 - Authenticated (Board Member+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 1.91.3
- Affected Plugin
- FluentBoards – Project Management, Task Management, Goal Tracking, Kanban Board, and, Team Collaboration
- Affected Version
<= 1.91.2- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-40784
At a glance
CVE-2026-40784 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the FluentBoards WordPress plugin, affecting versions <= 1.91.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Board Member level or above. The issue is fixed in version 1.91.3; sites on affected versions should update now. Disclosed April 2026, reported by Jakub Herman.
Vulnerability Overview
The FluentBoards – Project Management, Task Management, Goal Tracking, Kanban Board, and, Team Collaboration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.91.2 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Custom-level access and above, to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in FluentBoards <= 1.91.2 takes an account at Board Member level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For FluentBoards the fix is 1.91.3: builds <= 1.91.2 are affected, anything from 1.91.3 onward is not.
Remediation
Update to version 1.91.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: FluentBoards 1.91.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in FluentBoards – Project Management, Task Management, Goal Tracking, Kanban Board, and, Team Collaboration
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C