LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69293: WordPress Final User plugin <= 1.2.5 - Privilege Escalation vulnerability

Incorrect Privilege Assignment vulnerability in e-plugins Final User final-user allows Privilege Escalation.This issue affects Final User: from n/a through <= 1.2.5.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69293 is a high-severity privilege escalation issue in the WordPress Final User plugin up to version 1.2.5. A low-privileged user may be able to gain higher privileges, risking site takeover, data exposure, and content or configuration changes. No cited source confirms active exploitation.

Executive priority

Prioritize within the normal high-severity WordPress vulnerability process, especially for sites allowing public user accounts. Business risk is elevated because successful exploitation could lead to administrative control or major site impact. Urgency depends on whether the plugin is installed and exposed to untrusted users.

Technical view

The CVE describes incorrect privilege assignment, mapped to CWE-266, in e-plugins Final User for WordPress through 1.2.5. CVSS 3.1 is 8.8: network exploitable, low complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress installations running the Final User plugin version 1.2.5 or earlier. The CVE data indicates an authenticated low-privilege attacker is required, so public registration, subscriber accounts, or compromised low-level accounts increase risk.

Exploitation context

The provided sources do not state that this vulnerability is actively exploited, and it is not marked KEV in the supplied data. The CVSS vector indicates exploitation could occur remotely by a low-privileged authenticated user without user interaction.

Researcher notes

The source bundle provides CVE metadata and a Patchstack database reference, but no detailed root cause, proof of concept, exploit status, or fixed-version information. Avoid assuming a patch exists until confirmed by vendor or Patchstack guidance. The affected-version statement is through 1.2.5.

Mitigation direction

  • Identify all WordPress sites using the Final User plugin.
  • Check whether installed plugin versions are 1.2.5 or earlier.
  • Review Patchstack and vendor guidance for fixed versions or official mitigation.
  • Disable or remove the plugin if no safe version is available.
  • Restrict creation and use of low-privileged WordPress accounts where feasible.

Validation and detection

  • Inventory WordPress plugins across production and staging sites.
  • Confirm Final User plugin version from WordPress administration or asset records.
  • Review user registration settings and low-privilege account exposure.
  • Check WordPress logs for unusual role or capability changes.
  • Monitor Patchstack and CVE records for updated remediation details.
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-69293 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
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
e-pluginsFinal Userfinal-user, 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.