dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-67909

HIGH · 7.5 CVSS v3.1 Published 2025-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization Bypass Through User-Controlled Key vulnerability in WP Swings Membership For WooCommerce membership-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Membership For WooCommerce: from n/a through <= 3.0.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authorization bypass vulnerability in the WP Swings Membership For WooCommerce plugin allows attackers to exploit incorrectly configured access control security levels through user-controlled keys. This enables unauthorized access to membership functionality and potentially sensitive content without proper authentication validation.

MitigationUpdate the Membership For WooCommerce plugin to the latest version beyond 3.0.3 to obtain the patched version with proper access control implementation. If immediate update is not possible, audit user access roles and restrict administrative access to membership settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Navigate to WordPress admin > Plugins and locate 'Membership For WooCommerce' by WP Swings. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'membership-for-woocommerce' or similar naming pattern.
    Affected if The plugin is installed and active on the WooCommerce site.
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin to view version details, or inspect the main plugin PHP file header for a 'Version:' tag. Compare this version number to 3.0.3.
    Affected if The installed version is 3.0.3 or lower.
  3. Verify membership functionality is enabled
    Navigate to WordPress admin > Membership (or WooCommerce > Memberships) and confirm that at least one membership plan is published and active. Check if any membership content restrictions or protected pages exist.
    Affected if Membership plans are active and membership-protected content exists on the site.
  4. Inspect access control configuration
    Go to plugin settings for Membership For WooCommerce and review any access control, permission, or role-based settings. Look for options related to 'access levels,' 'user roles,' or 'membership access keys.'
    Affected if Access control settings are configured with user-controlled keys, custom roles, or non-default permission levels.
  5. Review API or key-based authentication settings
    Check plugin settings for any API key, access token, or 'key' fields that may be user-configurable. Inspect WooCommerce REST API settings and any custom endpoints related to membership functionality.
    Affected if User-configurable keys or tokens are defined in the plugin or WooCommerce API settings.

A site is affected if the Membership For WooCommerce plugin version is 3.0.3 or lower, membership plans are active, and user-controlled keys or access control configurations are present that could allow unauthorized access to membership functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Membership For WooCommerce plugin to the latest version beyond 3.0.3 to obtain the patched version with proper access control implementation. If immediate update is not possible, audit user access roles and restrict administrative access to membership settings.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67909 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data