dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-15030

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-02
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 User Profile Builder WordPress plugin before 3.15.2 does not have a proper password reset process, allowing a few unauthenticated requests to reset the password of any user by knowing their username, such as administrator ones, and therefore 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 User Profile Builder WordPress plugin before version 3.15.2 contains a critical authentication flaw in its password reset mechanism. The plugin does not properly validate password reset requests, allowing unauthenticated attackers to reset any user's password by simply knowing their username. This enables complete account takeover of administrator and other privileged accounts.

MitigationUpdate User Profile Builder plugin to version 3.15.2 or later to obtain the patched password reset functionality. If immediate update is not possible, consider disabling user registration or implementing additional authentication controls.

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. Identify if User Profile Builder plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or check the /wp-content/plugins/ directory for a folder containing 'user-profile-builder'
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find User Profile Builder and read the version number displayed under the plugin name. Alternatively, check the main plugin PHP file for the 'Version' header comment
    Affected if Version is lower than 3.15.2 (e.g., 3.15.1, 3.14.x, earlier versions)
  3. Verify user registration is enabled
    In WordPress admin > Settings > General, check the 'Membership' setting - ensure 'Anyone can register' is unchecked. Also check User Profile Builder settings for any front-end registration forms that may be enabled
    Affected if User registration is enabled and the password reset functionality is accessible to unauthenticated users
  4. Review access logs for password reset activity
    Examine web server access logs (Apache/Nginx) for repeated POST requests to /wp-login.php?action=lostpassword or custom password reset endpoints, especially from multiple IP addresses targeting various usernames
    Affected if Unusual pattern of password reset requests for administrative or privileged usernames, especially from unauthenticated sources

The site is affected if User Profile Builder plugin version is below 3.15.2 and user registration or password reset functionality is accessible to unauthenticated users.

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 User Profile Builder plugin to version 3.15.2 or later to obtain the patched password reset functionality. If immediate update is not possible, consider disabling user registration or implementing additional authentication controls.

Recommended fix Moderate confidence

User Profile Builder 3.15.2 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the User Profile Builder plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 3.15.2 or later
  5. 5. Alternatively, upload the User Profile Builder version 3.15.2 or newer plugin files via Plugins > Add New > Upload Plugin
  6. 6. Verify the plugin version is 3.15.2 or newer after updating
  7. 7. Test the password reset functionality to confirm it now requires proper authentication
Caveat Review plugin changelog and test in staging environment before production deployment as minor incompatibilities may exist with other plugins or themes

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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