dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-2266

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-29
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
The Checkout Mestres do WP for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the cwmpUpdateOptions() function in versions 8.6.5 to 8.7.5. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 · high confidence

The Checkout Mestres do WP plugin for WooCommerce has a missing capability check on the cwmpUpdateOptions() function in versions 8.6.5-8.7.5, allowing unauthenticated attackers to update arbitrary WordPress options. Attackers exploit this by changing the default user registration role to Administrator and enabling user registration, then registering an admin account to fully compromise the site.

MitigationImmediately update the plugin to the latest version or remove/disable it if no patch exists. Audit for unauthorized admin accounts created via this vulnerability and remove them. Force reset passwords for all existing administrator accounts as a precaution.

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. Confirm plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Checkout Mestres do WP' or 'Mestres do WP' or check the wp-content/plugins directory for a folder containing 'mestres' or 'cwmp' in the name
    Affected if The plugin is present on the site
  2. Check installed plugin version
    In WordPress admin > Plugins, find the plugin and view the version number. Compare it to version 8.7.6 - versions below 8.7.6 are vulnerable
    Affected if The installed version is lower than 8.7.6
  3. Verify user registration is enabled
    Go to WordPress admin > Settings > General and check if 'Membership - Anyone can register' is checked. Also check if the 'New User Default Role' is set to Administrator
    Affected if User registration is enabled with Administrator as the default role, especially if you did not enable this yourself
  4. Audit admin user accounts
    Go to WordPress admin > Users and review all accounts with Administrator role. Look for unfamiliar accounts, accounts created around the same time, or accounts you did not create
    Affected if There are administrator accounts you did not create or that were created recently

A site is affected if the Checkout Mestres do WP plugin below version 8.7.6 is installed and either user registration has been enabled with admin default role or unauthorized admin accounts exist.

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

Immediately update the plugin to the latest version or remove/disable it if no patch exists. Audit for unauthorized admin accounts created via this vulnerability and remove them. Force reset passwords for all existing administrator accounts as a precaution.

Recommended fix Moderate confidence

Version 8.7.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Checkout Mestres do WP for WooCommerce'
  4. 4. If an update is available, click 'Update Now'
  5. 5. Verify the updated version is 8.7.6 or higher
  6. 6. Confirm the site still functions correctly after the update

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

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-2266 — 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-2266 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