dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-15403

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-17
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 RegistrationMagic plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 6.0.7.1. This is due to the 'add_menu' function is accessible via the 'rm_user_exists' AJAX action and allows arbitrary updates to the 'admin_order' setting. This makes it possible for unauthenticated attackers to injecting an empty slug into the order parameter, and manipulate the plugin's menu generation logic, and when the admin menu is subsequently built, the plugin adds 'manage_options' capability for the target role. Note: The vulnerability can only be exploited unauthenticated, but further privilege escalation requires at least a subscriber user.

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 RegistrationMagic WordPress plugin allows unauthenticated attackers to manipulate the 'admin_order' setting via the 'rm_user_exists' AJAX action. By injecting an empty slug into the order parameter, attackers manipulate the plugin's menu generation logic to add 'manage_options' capability to arbitrary roles, enabling privilege escalation.

MitigationUpdate RegistrationMagic to version 6.0.7.2 or later. Until patched, disable the plugin or add firewall rules to block the 'rm_user_exists' AJAX action for unauthenticated users.

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. Locate RegistrationMagic plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'registrationmagic' or 'registration-magic'. Read the main plugin file (typically registrationmagic.php) to find the version declared in the plugin header comment.
    Affected if The plugin folder exists and the version is below 6.0.7.2 or the version cannot be determined
  2. Verify AJAX endpoint exposure
    Check if the rm_user_exists AJAX action is accessible to unauthenticated users by examining the plugin's code for add_action('wp_ajax_rm_user_exists') or add_action('wp_ajax_nopriv_rm_user_exists'). Also test by sending a POST request to /wp-admin/admin-ajax.php with action=rm_user_exists and no authentication cookies.
    Affected if The AJAX action is registered with wp_ajax_nopriv_ hook or responds without authentication
  3. Inspect admin_order parameter handling
    Examine the plugin code for how the 'admin_order' parameter is processed in the rm_user_exists AJAX handler. Look for code that uses this parameter to manipulate role capabilities or menu generation logic.
    Affected if The code accepts and processes the admin_order parameter without sanitization in a way that can modify role capabilities
  4. Check for privilege escalation indicators
    Review any custom roles or capabilities in the WordPress database. Look for unexpected manage_options capabilities added to roles that should not have administrative privileges.
    Affected if Roles have been granted manage_options capability through plugin-induced modifications

A user is affected if RegistrationMagic plugin version is below 6.0.7.2 AND the rm_user_exists AJAX endpoint is accessible to unauthenticated users, allowing them to inject admin_order parameters that modify role capabilities.

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 RegistrationMagic to version 6.0.7.2 or later. Until patched, disable the plugin or add firewall rules to block the 'rm_user_exists' AJAX action for unauthenticated users.

Recommended fix High confidence

RegistrationMagic version 6.0.8.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'RegistrationMagic' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 6.0.8.0 from the WordPress plugin repository
  5. Verify the plugin updated to version 6.0.8.0 or later
  6. Confirm the site functions normally 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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