dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-10038

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 Binary MLM Plan plugin for WordPress is vulnerable to limited Privilege Escalation in all versions up to, and including, 3.0. This is due to bmp_user role granting all users with the manage_bmp capability by default upon registration through the plugin's form. This makes it possible for unauthenticated attackers to register and manage the plugin's settings.

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 Binary MLM Plan WordPress plugin (versions up to 3.0) grants the manage_bmp capability to all users registering through its form by default via the bmp_user role. This allows unauthenticated attackers to self-register on the site and automatically receive privileges to access and modify the plugin's settings, representing a privilege escalation vulnerability.

MitigationUpdate to a patched version of the plugin when released; until then, disable the plugin's user registration form or restrict site registration entirely, and audit existing bmp_user role accounts for unauthorized access.

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
Low
Integrity
Low
Availability
None

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

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. Identify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Binary MLM Plan'. Check the version number listed. Compare to affected versions (up to 3.0).
    Affected if Binary MLM Plan plugin is installed and version is 3.0 or lower
  2. Verify bmp_user role exists with manage_bmp capability
    Use a role editor plugin or WP-CLI: `wp role list` to list roles, then `wp cap list bmp_user` to see capabilities. Alternatively, check wp_options for role definitions or use a database query to inspect the wp_roles option.
    Affected if A role named 'bmp_user' exists and includes the 'manage_bmp' capability
  3. Confirm plugin user registration form is accessible
    Visit the registration page URL provided by the plugin (commonly /binary-mlm-registration or similar). Try submitting a registration without authentication to see if new users are created with bmp_user role.
    Affected if The plugin registration form is publicly accessible and creates accounts with bmp_user role without admin approval
  4. Audit existing bmp_user role accounts
    Query the WordPress database: SELECT u.user_login, u.user_email FROM wp_users u JOIN wp_usermeta m ON u.ID = m.user_id WHERE m.meta_key = 'wp_capabilities' AND m.meta_value LIKE '%bmp_user%'. Or use WP-CLI: `wp user list --role=bmp_user`.
    Affected if Any unexpected or unauthorized users have the bmp_user role, especially those not created by site administrators
  5. Check WordPress user registration settings
    Navigate to WordPress Settings > General > 'Membership' and verify if 'Anyone can register' is enabled. If enabled with Binary MLM Plan active, unauthenticated self-registration is possible.
    Affected if 'Anyone can register' is enabled and Binary MLM Plan plugin handles the registration, automatically assigning bmp_user role

A user is affected if the Binary MLM Plan plugin (version 3.0 or below) is installed, the bmp_user role with manage_bmp capability exists, and the plugin's registration form allows unauthenticated users to self-register with elevated plugin access.

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 when released; until then, disable the plugin's user registration form or restrict site registration entirely, and audit existing bmp_user role accounts for unauthorized access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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