CVE-2026-78466
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
The Fluent Boards Pro plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0.11 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.
Risk Assessment
IDOR can allow an attacker to access other users' resources or perform actions without proper authorization, potentially leading to confidentiality and integrity breaches.
Recommendation
Update the Fluent Boards Pro plugin to a version newer than 2.0.11 and implement proper access validation for resources.
Other vulnerabilities in Fluent Boards Pro
See all- CVE-2026-78278Medium
IDOR vulnerability in Fluent Boards Pro versions up to 2.0.11, affecting subscriber role users. Allows access to unauthorized objects.
- CVE-2026-78274Critical
The Fluent Boards Pro plugin versions up to 2.0.11 contain an arbitrary file upload vulnerability exploitable by users with the editor role. This can lead to execution of malicious code on the server.
- CVE-2026-78276High
Editor PHP Object Injection vulnerability in Fluent Boards Pro versions up to 2.0.11. A user with editor role can inject malicious PHP objects, potentially leading to remote code execution.
- CVE-2026-78275Medium
The Fluent Boards Pro plugin version 2.0.11 and earlier has an Editor Arbitrary File Deletion vulnerability. An editor can delete arbitrary files on the server, which can lead to serious damage.
- CVE-2026-78273Medium
The Fluent Boards Pro plugin version 2.0.11 and earlier has a Subscriber Cross Site Scripting (XSS) vulnerability. A user with the subscriber role can inject a malicious script that executes in other users' browsers.
Original NVD description (English source)
The Fluent Boards Pro plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0.11 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.