dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-32695

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-09
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 Mestres do WP Checkout Mestres WP checkout-mestres-wp allows Privilege Escalation.This issue affects Checkout Mestres WP: from n/a through <= 8.7.5.

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

The Checkout Mestres WP WordPress plugin versions 8.7.5 and below contains an Incorrect Privilege Assignment vulnerability that allows authenticated users to escalate their privileges, likely through improper role or capability validation in the checkout functionality.

MitigationUpdate the Checkout Mestres WP plugin to the latest version immediately and audit user accounts for unauthorized privilege escalation.

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 Checkout Mestres WP plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder containing 'mestres' or 'checkout-mestres'
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, click on the plugin to view its details and locate the version number, or open the main plugin PHP file (e.g., checkout-mestres-wp.php) and read the 'Version' header in the plugin comment block
    Affected if The version number displayed is 8.7.5 or lower, or if no version is displayed and the plugin file exists in version 8.7.5 or below
  3. Confirm checkout functionality is accessible to authenticated users
    Review the plugin settings in WordPress admin under the plugin menu, or examine the plugin PHP files for checkout-related functions and capability checks (look for 'add_action' or 'add_shortcode' handling checkout or payment processing)
    Affected if The plugin includes a checkout feature that processes user roles or capabilities without proper authorization checks
  4. Audit WordPress user accounts for unexpected privilege escalation
    In WordPress admin, go to Users > All Users and review the role assigned to each account; check for any users with Administrator or elevated roles they should not possess, or query the wp_usermeta table for role changes
    Affected if Any user account has been assigned a higher privilege role than originally intended, or new Administrator accounts exist that were not created by known admins

The environment is affected if the Checkout Mestres WP plugin versions 8.7.5 or below is installed and the checkout functionality is active, particularly if unauthorized privilege escalation is observed in user accounts.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Checkout Mestres WP plugin to the latest version immediately and audit user accounts for unauthorized privilege escalation.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 8.7.5)

  1. Check the current version of the Checkout Mestres WP plugin installed on your WordPress site
  2. If the installed version is <= 8.7.5, navigate to WordPress admin > Plugins > check for available updates
  3. Update the Checkout Mestres WP plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the plugin is functioning correctly
  5. Consider reviewing user roles and capabilities to ensure no unauthorized privilege changes occurred
Caveat Review plugin settings after upgrade as configuration may need adjustment

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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