LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40205: WordPress wpForo Forum plugin <= 2.0.5 - Insecure direct object references (IDOR) vulnerability

Insecure direct object references (IDOR) vulnerability in the wpForo Forum plugin <= 2.0.5 on WordPress allows attackers with subscriber or higher user roles to mark any forum post as solved/unsolved.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A logged-in low-privilege WordPress user could change the solved or unsolved status of forum posts they should not control. This can damage forum workflow integrity and user trust, but the bundle does not show data theft or full site compromise.

Executive priority

Treat as a moderate-priority integrity issue. Prioritize remediation for public forums, customer support forums, or communities where solved status drives trust, support workflow, or service reporting.

Technical view

CVE-2022-40205 is a CWE-639 insecure direct object reference in gVectors Team wpForo Forum for WordPress versions up to 2.0.5. A subscriber-or-higher user can mark arbitrary forum posts solved or unsolved, affecting integrity and limited availability of forum content state.

Likely exposure

Exposure is limited to WordPress sites running wpForo Forum version 2.0.5 or earlier, especially sites allowing public account registration or many subscriber-level users.

Exploitation context

The source bundle does not cite active exploitation, KEV listing, or public exploit use. Abuse requires an authenticated WordPress account with subscriber or higher privileges, reducing unauthenticated risk but increasing concern for open-registration forums.

Researcher notes

Assess this as authenticated IDOR affecting authorization on forum post state changes. The provided evidence supports impact to integrity and limited availability only; it does not support confidentiality impact, unauthenticated exploitation, or broader WordPress compromise.

Mitigation direction

  • Inventory WordPress sites for wpForo Forum installations and versions.
  • Update wpForo Forum using official WordPress or vendor guidance.
  • Confirm the installed version is outside the affected range.
  • Restrict public registration or subscriber access until remediation is verified.
  • Review forum moderation logs for unexpected solved or unsolved status changes.

Validation and detection

  • Check whether wpForo Forum is installed on each WordPress site.
  • Verify plugin version is not 2.0.5 or earlier.
  • Identify whether public registration grants subscriber-level access.
  • Review recent forum post status changes for unauthorized activity.
  • Confirm vendor or WordPress plugin guidance has been applied.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40205 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-40205Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gVectors TeamwpForo Forum (WordPress plugin)<= 2.0.5Listed
Weakness

CWE details

CWE-639

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs