LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47868: WordPress wpForo plugin <= 2.2.3 - Privilege Escalation vulnerability

Improper Privilege Management vulnerability in wpForo wpForo Forum allows Privilege Escalation.This issue affects wpForo Forum: from n/a through 2.2.3.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-47868 affects the WordPress wpForo Forum plugin through version 2.2.3. The issue is improper privilege management, which can let an attacker gain unauthorized privileges. The CVSS vector indicates remote attack, low complexity, no required login, and no user interaction. Sites using affected plugin versions should prioritize verification and remediation.

Executive priority

Prioritize remediation for public WordPress sites using wpForo Forum, especially customer-facing forums. The vulnerability is high severity and appears remotely reachable without authentication, but the provided sources do not confirm active exploitation.

Technical view

The CVE records CWE-269 improper privilege management in wpForo Forum through 2.2.3, with CVSS 3.1 score 7.3. The vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L indicates unauthenticated network reachability with limited confidentiality, integrity, and availability impact. Public details provided do not describe the vulnerable code path or exact privilege boundary bypass.

Likely exposure

Exposure is likely limited to WordPress sites with wpForo Forum installed at version 2.2.3 or earlier. Public forums are internet-facing by design, increasing practical reachability.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk remains meaningful because the CVSS vector indicates unauthenticated, low-complexity remote exploitation conditions.

Researcher notes

The public bundle identifies the weakness class, affected plugin range, and CVSS vector, but not root-cause details, proof of concept, or exact fixed release. Validation should stay version-based and log-focused unless vendor advisories provide deeper technical indicators.

Mitigation direction

  • Inventory WordPress sites for the wpForo Forum plugin and installed version.
  • Treat wpForo Forum versions through 2.2.3 as affected.
  • Review wpForo or Patchstack guidance for the fixed version and update path.
  • Restrict administrative access and review forum user roles until remediation is complete.
  • Monitor WordPress, web server, and plugin logs for unusual role or permission changes.

Validation and detection

  • Confirm whether wpForo Forum is installed on each WordPress site.
  • Record the installed plugin version and compare it with the affected range through 2.2.3.
  • Check whether any unexpected privileged users or role changes exist.
  • Verify remediation by confirming the installed version is outside the affected range.
  • Document exception status for sites where vendor remediation is not yet available.
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 · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2023-47868 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
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.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2023-47868Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
wpForowpForo Forumwpforo, n/aunaffected
Weakness

CWE details

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