LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69193: WordPress WP Membership plugin <= 1.6.4 - Broken Access Control vulnerability

Missing Authorization vulnerability in e-plugins WP Membership wp-membership allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Membership: from n/a through <= 1.6.4.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69193 is a high-severity access-control flaw in the WordPress WP Membership plugin from e-plugins, affecting versions through 1.6.4. A remote unauthenticated attacker may be able to bypass intended authorization checks, with limited confidentiality, integrity, and availability impact. Public sources do not confirm active exploitation or a fixed version.

Executive priority

Treat as a near-term priority for WordPress environments using WP Membership. The business risk is unauthorized access or changes in membership-protected functions. Prioritize identification, vendor guidance review, and risk-based removal or update decisions.

Technical view

The issue is CWE-862 Missing Authorization in wp-membership. The CVSS 3.1 score is 7.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, with low C/I/A impact. The CVE describes exploitation of incorrectly configured access control security levels in WP Membership through version 1.6.4.

Likely exposure

Exposure is limited to WordPress sites running the WP Membership plugin package wp-membership at version 1.6.4 or earlier, especially internet-facing sites. Sites not using this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates remote unauthenticated exploitation without user interaction. The source bundle does not include exploit details, proof-of-concept status, or evidence of active exploitation. The CVE is not listed as KEV in the provided data.

Researcher notes

Public detail is sparse. The available record identifies missing authorization but does not describe affected endpoints, required configuration, exploit maturity, or remediation version. Avoid assuming a patch exists unless confirmed by vendor or Patchstack guidance.

Mitigation direction

  • Inventory WordPress sites for the WP Membership plugin.
  • Confirm whether wp-membership is version 1.6.4 or earlier.
  • Check e-plugins, WordPress.org, and Patchstack for updated vendor guidance.
  • If no safe update exists, consider disabling the plugin after business review.
  • Increase monitoring for unauthorized membership or access-control changes.

Validation and detection

  • Review WordPress plugin inventory for wp-membership installations.
  • Record installed plugin versions across production and staging sites.
  • Compare installed versions against the affected range through 1.6.4.
  • Check web and WordPress logs for suspicious access-control activity.
  • Document compensating controls if the plugin must remain active.
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-862: 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
cve · low confidence lookup

CVE-2025-69193 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-2025-69193Attack 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
e-pluginsWP Membershipwp-membership, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

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