LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40206: 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 private/public.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-40206 affects the wpForo Forum WordPress plugin through version 2.0.5. A logged-in user with subscriber-level access or higher could change forum posts between private and public states, potentially exposing restricted content or hiding visible content.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It is not described as actively exploited, but it can affect confidentiality and integrity on community forums with user accounts.

Technical view

The issue is an insecure direct object reference mapped to CWE-639. The reported authorization weakness allows authenticated low-privilege users to alter privacy status for arbitrary forum posts. CVSS 3.1 is 6.3, reflecting low-complexity network access with required privileges.

Likely exposure

Exposure is limited to WordPress sites using wpForo Forum version 2.0.5 or earlier and allowing subscriber or higher accounts. Public registration increases practical exposure.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Abuse requires an authenticated account, but subscriber access is commonly available on community sites.

Researcher notes

Evidence supports an authenticated IDOR affecting post privacy controls in wpForo Forum <= 2.0.5. Sources do not provide exploit details, a named fixed version, or independent exploitation telemetry in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for the wpForo Forum plugin.
  • Upgrade wpForo Forum per current vendor or WordPress plugin guidance.
  • Do not leave wpForo Forum at version 2.0.5 or earlier.
  • Review subscriber and contributor accounts for unnecessary access.
  • Check forum moderation logs for unexpected private or public status changes.

Validation and detection

  • Confirm whether wpForo Forum is installed on each WordPress site.
  • Record the installed plugin version and flag versions 2.0.5 or earlier.
  • Review whether public user registration is enabled.
  • Verify only authorized roles can change forum post privacy state.
  • Check recent forum posts for unexplained visibility changes.
Prepared
Confidence
medium
Sources
4

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-40206 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
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
Affected products

Products and packages named in the record

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

CWE details

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.