LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31420: WordPress wpForo Forum plugin <= 2.4.2 - Privilege Escalation vulnerability

Incorrect Privilege Assignment vulnerability in Tomdever wpForo Forum wpforo allows Privilege Escalation.This issue affects wpForo Forum: from n/a through <= 2.4.2.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-31420 affects the WordPress wpForo Forum plugin through version 2.4.2. A logged-in user could receive privileges they should not have, creating risk of unauthorized administrative actions or content changes. The CVSS score is high, but the provided sources do not state active exploitation.

Executive priority

Prioritize remediation for internet-facing WordPress sites using wpForo Forum, especially where users can self-register. The main business risk is unauthorized privilege gain leading to content, configuration, or forum integrity impact. No active exploitation is evidenced in the supplied sources.

Technical view

The issue is an incorrect privilege assignment flaw, mapped to CWE-266, in Tomdever wpForo Forum. The CVSS v3.1 vector indicates network access, low attack complexity, low privileges required, no user interaction, unchanged scope, low confidentiality impact, high integrity impact, and low availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running wpForo Forum at version 2.4.2 or earlier, especially sites allowing untrusted or broadly registered users to log in. Sites without the plugin, or running versions outside the affected range, are not indicated as affected by the source bundle.

Exploitation context

The source bundle does not identify active exploitation, and the CVE is not listed as KEV. A public Patchstack vulnerability entry exists. The attacker model requires an authenticated low-privilege account, so public registration and weak account controls increase practical risk.

Researcher notes

Evidence is sufficient for affected product, version boundary, CVSS, CWE, and attacker prerequisites. The bundle does not provide root-cause details, exploit mechanics, confirmed exploitation, or a named fixed version. Avoid assuming specific exploit paths or remediation versions beyond vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the wpForo Forum plugin and installed version.
  • Treat wpForo Forum version 2.4.2 or earlier as affected.
  • Check vendor, WordPress plugin, or Patchstack guidance for the fixed release.
  • Update the plugin when a trusted fixed version is confirmed.
  • Restrict untrusted user registration until remediation is complete.
  • Review user roles for unexpected privilege changes.

Validation and detection

  • Confirm whether wpForo Forum is installed on each WordPress site.
  • Record the plugin version and compare it with the affected range.
  • Review recent user role and capability changes for anomalies.
  • Check administrative activity for unexpected forum or site changes.
  • After remediation, confirm the vulnerable version is no longer deployed.
Prepared
Confidence
medium
Sources
3

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-266: 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31420 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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
2Source 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
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2025-31420Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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
TomdeverwpForo Forumwpforo, 0unaffected
Weakness

CWE details

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

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.