CVE-2025-15030

User Profile Builder <= 3.15.1 - Unauthenticated Privilege Escalation via Account Takeover

2026-01-12 00:00
Drew Webber (mcdruid)

Strategic Overview

At a glance

CVE-2025-15030 is a critical-severity Unverified Password Change vulnerability in the User Profile Builder WordPress plugin, affecting versions <= 3.15.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.15.2; sites on affected versions should update now. Disclosed January 2026, reported by Drew Webber (mcdruid).

Vulnerability Overview

The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.15.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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-620: Unverified Password Change

Reaching this weakness in User Profile Builder <= 3.15.1 takes no account at all. Unverified password change means the password-update path does not require proof that the requester is the account owner.

An attacker who can reach the endpoint takes over the account outright, and the legitimate owner is locked out of it. For User Profile Builder the fix is 3.15.2: builds <= 3.15.1 are affected, anything from 3.15.2 onward is not.

Remediation

Update to version 3.15.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: User Profile Builder 3.15.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C