Subscriber-level post privacy change via IDOR
Published Nov 8, 2022 · Updated Apr 28, 2026
Authentication bypass in wpForo Forum <= 2.0.5 allows remote authenticated users to mark any forum post private or public. The published records do not identify the vulnerable endpoint, parameter, function, or direct-object check, so the precise untrusted input operation remains undisclosed. Subscriber-level or higher WordPress access is required, and the demonstrated consequence is unauthorized alteration of forum-post visibility rather than arbitrary code execution.
Summary
What happened
Authentication bypass in wpForo Forum <= 2.0.5 allows remote authenticated users to mark any forum post private or public. The published records do not identify the vulnerable endpoint, parameter, function, or direct-object check, so the precise untrusted input operation remains undisclosed. Subscriber-level or higher WordPress access is required, and the demonstrated consequence is unauthorized alteration of forum-post visibility rather than arbitrary code execution.
The record
- CVE
- CVE-2022-40206
- Published
- Nov 8, 2022
- Updated
- Apr 28, 2026
- Vendor
- AdvancedCoding
- Product
- wpForo Forum
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2.0.5 <=2.0.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo