wpForo Forum <= 2.0.5 - Insecure Direct Object Reference to Forum Privacy Change
Strategic Overview
- Status
- Patched in 2.0.6
- Affected Plugin
- wpForo Forum
- Affected Version
<= 2.0.5- CVSS
- 6.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2022-40206
At a glance
CVE-2022-40206 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the wpForo Forum WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed November 2022, reported by Dhakal Ananda.
Vulnerability Overview
The wpForo Forum plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.0.5. This makes it possible for authenticated attackers, with subscriber-level access or higher, to mark any forum post as private/public.
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 wpForo Forum <= 2.0.5 takes a caller who can reach the endpoint. 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 wpForo Forum the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.
Remediation
Update to version 2.0.6, 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: wpForo Forum 2.0.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.4CVE-2022-40205: wpForo Forum <= 2.0.5 IDOR to Forum Status Change
CVE-2022-40205 - 4.3CVE-2026-12697: wpForo Forum IDOR
CVE-2026-12697 - 4.3CVE-2025-58597: wpForo Forum <= 2.4.6 Insecure Direct Object Reference
CVE-2025-58597 - 4.3CVE-2024-43288: wpForo Forum <= 2.3.4 Insecure Direct Object Reference
CVE-2024-43288
Other vulnerabilities in wpForo Forum
- 9.9CVE-2024-3200: wpForo Forum <= 2.3.3 SQL Injection
CVE-2024-3200 - 9.8CVE-2023-47868: wpForo Forum <= 2.2.3 Privilege Escalation
CVE-2023-47868 - 9.8CVE-2018-16613: wpForo < = 1.5.1 Privilege Escalation
CVE-2018-16613 - 9.8CVE-2018-11515: wpForo Forum <= 1.4.12 SQL Injection
CVE-2018-11515 - 8.8CVE-2026-3666: wpForo Forum <= 2.4.16 Arbitrary File Deletion
CVE-2026-3666 - 8.8CVE-2026-0910: wpForo Forum <= 2.4.13 PHP Object Injection
CVE-2026-0910 - 8.8CVE-2025-31420: wpForo Forum <= 2.4.3 Privilege Escalation
CVE-2025-31420 - 8.8CVE-2023-2249: wpForo Forum Local File Include, SSRF, and PHAR
CVE-2023-2249
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C