dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-15001

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-06
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 FS Registration Password plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.0.1. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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 FS Registration Password plugin for WordPress fails to validate user identity before permitting password changes, enabling unauthenticated attackers to reset any user's password including administrator accounts. This privilege escalation flaw allows complete account takeover by exploiting the missing authorization check in the password update mechanism.

MitigationUpgrade the FS Registration Password plugin to version 1.0.2 or later which includes proper identity validation before password modifications. If no patched version exists, disable the plugin immediately and implement alternative user management.

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 FS Registration Password plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'FS Registration Password' or 'fs-registration-password'
    Affected if The plugin appears in the list of installed plugins
  2. Check the installed plugin version
    In the Plugins list, locate FS Registration Password and note the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field
    Affected if The displayed version is 1.0.1 or lower, or if no version is shown but the plugin name matches
  3. Confirm the plugin is active
    In the Plugins list, verify the plugin has an 'Active' status under the plugin name
    Affected if The plugin is active and available for use on the site
  4. Check for suspicious admin account changes
    Review WordPress user accounts in Users > All Users for any unfamiliar administrative accounts created recently, or check server access logs for POST requests to /wp-admin/admin-ajax.php or the plugin's endpoints with unusual parameters
    Affected if New administrative accounts exist that were not created by legitimate administrators, or atypical password reset activity is logged

The environment is affected if the FS Registration Password plugin versions 1.0.1 or lower is installed and active on the WordPress site, enabling unauthenticated password change requests.

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

Upgrade the FS Registration Password plugin to version 1.0.2 or later which includes proper identity validation before password modifications. If no patched version exists, disable the plugin immediately and implement alternative user management.

Recommended fix Moderate confidence

Version 1.0.2 or later

  1. Check the current version of the FS Registration Password plugin in your WordPress installation
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate FS Registration Password and note the current version
  4. Update the plugin to the latest available version (1.0.2 or higher)
  5. If an update is not available, consider temporarily disabling the plugin until a fix is released
  6. After updating, verify that user passwords cannot be changed without proper authentication
  7. Consider forcing a password reset for administrator accounts as a precautionary measure

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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