dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-60222

HIGH · 8.8 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Privilege Assignment vulnerability in FantasticPlugins SUMO Memberships for WooCommerce sumomemberships allows Privilege Escalation.This issue affects SUMO Memberships for WooCommerce: from n/a through <= 7.8.0.

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

Incorrect Privilege Assignment vulnerability in SUMO Memberships for WooCommerce allows authenticated users to escalate their privileges beyond what their assigned role should permit, likely due to improper capability or role validation during membership level assignment.

MitigationUpdate to a patched version of the plugin; if unavailable, audit the membership role assignment logic and enforce proper capability checks to ensure users can only assign roles within their authorization level.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify SUMO Memberships for WooCommerce is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'SUMO Memberships for WooCommerce' or 'SUMO Memberships' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'sumo-memberships' or similar naming.
    Affected if The plugin is found installed in the WordPress environment
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the SUMO Memberships plugin to view its details. Note the version number displayed. Compare this version to 7.8.0 - any version at or below 7.8.0 is affected.
    Affected if The installed version is 7.8.0 or any earlier version
  3. Confirm user registration is enabled
    Navigate to WordPress Settings > General and check the box labeled 'Membership - Anyone can register'. If checked, any new user registration is allowed. Also check WooCommerce > Settings > Accounts > Enable registration, if using WooCommerce customer registration.
    Affected if User registration is enabled, allowing the privilege escalation to be exploited by newly registered low-privilege users
  4. Audit administrator-level accounts
    Go to WordPress Users > All Users and review the list of users with Administrator role. Identify any accounts that should not have administrative access, particularly accounts created recently or belonging to users who should only have Subscriber or Customer roles.
    Affected if There are unexpected administrator accounts, especially those created after the plugin was installed or belonging to users who did not receive admin privileges through legitimate admin actions
  5. Check for unusual capability assignments
    Use a user role editor plugin or query the wp_usermeta table to examine the wp_capabilities meta_value for non-admin users. Look for any subscribers or customers who have capabilities beyond their assigned role, such as 'manage_options' or 'edit_users'.
    Affected if Non-administrator users have administrative-level capabilities assigned to them

Your environment is affected if SUMO Memberships for WooCommerce version 7.8.0 or earlier is installed, user registration is enabled, and unexpected administrator accounts or elevated capabilities exist for low-privilege users.

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 to a patched version of the plugin; if unavailable, audit the membership role assignment logic and enforce proper capability checks to ensure users can only assign roles within their authorization level.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60222 — 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-60222 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