CVE-2022-40205

wpForo Forum <= 2.0.5 - Insecure Direct Object Reference to Forum Status Change

2022-09-26 09:03

Strategic Overview

Status: Patched in 2.0.6
Affected Plugin: wpForo Forum
Affected Version: <= 2.0.5
CVSS: 5.4Medium
Weakness type: CWE-639 · Authorization Bypass Through User-Controlled Key
CVE: CVE-2022-40205

At a glance

CVE-2022-40205 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 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed September 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 solved/unsolved.

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

https://www.cve.org/CVERecord?id=CVE-2022-40205 https://www.wordfence.com/threat-intel/vulnerabilities/id/ee78642c-ad2a-4012-94e8-e01f71863791 https://nvd.nist.gov/vuln/detail/CVE-2022-40205

Related records

Same weakness class

Other vulnerabilities in wpForo Forum

CVSS Vector

5.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityLow

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/