dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-60220

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
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
Incorrect Privilege Assignment vulnerability in pebas CouponXxL couponxxl allows Privilege Escalation.This issue affects CouponXxL: from n/a through <= 3.0.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 · low confidence

This is a privilege escalation vulnerability in the CouponXxL WordPress plugin by pebas. The 'Incorrect Privilege Assignment' classification indicates that the plugin improperly assigns or fails to properly validate user roles and capabilities, allowing lower-privileged users to gain administrative or elevated access they should not have.

MitigationUpdate to a patched version of CouponXxL beyond 3.0.0 if available, or implement proper capability checks and role-based access controls in the plugin code to ensure users can only access functionality appropriate to their privilege 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 CouponXxL plugin is installed
    Navigate to WordPress admin > Plugins and look for CouponXxL by pebas, or check the /wp-content/plugins/ directory for a couponxxl folder
    Affected if The CouponXxL plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin > Plugins, find CouponXxL and read the version number displayed beneath the plugin name, or open the main plugin file (usually couponxxl.php) and look for the 'Version' header comment
    Affected if The installed version is 3.0.0 or earlier, since the patched version is beyond 3.0.0
  3. Check for unexpected administrative users
    Go to WordPress admin > Users and review the list of users with Administrator role. Verify that only expected personnel have admin access and that no suspicious accounts were created
    Affected if There are administrator accounts that were not created by known administrators or that belong to users who should only have subscriber, editor, or author privileges
  4. Inspect plugin capability configurations
    Access the site via FTP or file manager, locate the CouponXxL plugin files, and search for functions that add_cap, add_role, or modify user capabilities. Check if any role/capability assignments allow low-privileged users to access admin functions
    Affected if The plugin creates custom roles or adds capabilities (like 'manage_options' or 'edit_users') to roles that should not have them (subscriber, contributor, etc.)
  5. Review user role assignments in the database
    Use a database tool (phpMyAdmin or CLI) to query the wp_usermeta table, looking at meta_key 'wp_capabilities' for non-admin users. Check if any subscriber, contributor, or author users have 'administrator' or elevated capabilities assigned
    Affected if Users with roles like subscriber, contributor, or author have administrator-level capabilities stored in their user meta

A user is affected if CouponXxL plugin version 3.0.0 or earlier is installed AND either unexpected admin accounts exist or low-privileged users have elevated capabilities due to improper role assignments in the plugin.

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 CouponXxL beyond 3.0.0 if available, or implement proper capability checks and role-based access controls in the plugin code to ensure users can only access functionality appropriate to their privilege level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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