LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40632: WordPress wpForo Forum plugin <= 2.0.5 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team wpForo Forum plugin <= 2.0.5 on WordPress leading to topic deletion.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-40632 is a CSRF issue in the wpForo Forum WordPress plugin through version 2.0.5. If a logged-in user with topic-deletion capability is tricked into a malicious interaction, forum topics could be deleted. Business impact is limited but real for sites relying on forum content availability and integrity.

Executive priority

Treat this as a moderate WordPress plugin maintenance issue. It is not reported as actively exploited here, but it can damage forum content and trust if outdated installations remain exposed.

Technical view

The flaw is CWE-352 in gVectors Team wpForo Forum <= 2.0.5. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact. The disclosed consequence is topic deletion.

Likely exposure

Exposure is limited to WordPress installations running wpForo Forum version 2.0.5 or earlier. Sites with active forums, moderators, or administrators who can delete topics face the most relevant operational risk.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation would require user interaction consistent with CSRF, likely involving a logged-in user whose browser can perform topic-deletion actions.

Researcher notes

Evidence identifies affected product, version range, CWE, CVSS vector, and topic deletion impact. The source bundle does not include exploit details, fixed-version text, or proof of exploitation, so remediation should follow vendor and WordPress plugin guidance.

Mitigation direction

  • Inventory WordPress sites for wpForo Forum and confirm installed versions.
  • Update wpForo through the official WordPress plugin channel or vendor guidance.
  • If update cannot be completed, temporarily disable wpForo on exposed sites.
  • Restrict topic-deletion permissions to necessary trusted roles only.
  • Back up forum content before remediation or plugin changes.

Validation and detection

  • Check WordPress admin plugin inventory for wpForo version 2.0.5 or earlier.
  • Confirm production sites run a vendor-supported version after remediation.
  • Review forum moderation history for unexpected topic deletions.
  • Verify only intended roles can delete topics.
  • Document affected sites, remediation date, and residual exceptions.
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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-40632 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:N/UI:R/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:N/UI:R/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-40632Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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-352

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs