User Profile Builder <= 4.0.3 - Unauthenticated Privilege Escalation to 'role' Parameter via Legacy Meta-Name Collision on [wppb-register]
Strategic Overview
- Status
- Patched in 4.0.4
- Affected Plugin
- User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
- Affected Version
<= 4.0.3- CVSS
- 8.1High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-109447
At a glance
CVE-2026-109447 is a high-severity Improper Privilege Management vulnerability in the User Profile Builder WordPress plugin, affecting versions <= 4.0.3. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.0.4; sites on affected versions should update now. Disclosed October 2026, reported by Supakiad S. (m3ez).
Vulnerability Overview
The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.0.3 via the `role` parameter handled by the `wppb_add_meta_to_user_on_activation()` function. The vulnerability exists because the activation handler passes the attacker-supplied role value directly to `WP_User::set_role()` with no allow-list validation, and the 4.0.3 reserved-name check exempts pre-existing form fields from the block, allowing a legacy field with meta-name `role` to persist and bridge attacker-controlled request input into the serialized signup record stored in `wp_signups`. This makes it possible for unauthenticated attackers to gain a fully activated WordPress administrator account by submitting `role=administrator` through the public `[wppb-register]` shortcode form and subsequently clicking the confirmation activation link. Exploitation requires the site to have a legacy form field with meta-name `role` carried over from before the 4.0.3 upgrade, email confirmation enabled, and open user registration — all stable site-state conditions once established.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, 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-269: Improper Privilege Management
User Profile Builder <= 4.0.3 carries this weakness at wppb_add_meta_to_user_on_activation(), and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For User Profile Builder the fix is 4.0.4: builds <= 4.0.3 are affected, anything from 4.0.4 onward is not.
Remediation
Update to version 4.0.4, 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 4.0.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
- 9.8CVE-2026-15826: User Profile Builder <= 3.16.4 Authentication Bypass
CVE-2026-15826 - 9.8CVE-2025-15030: User Profile Builder <= 3.15.1 Privilege Escalation
CVE-2025-15030 - 9.8CVE-2024-6695: User Profile Builder Authentication Bypass
CVE-2024-6695 - 9.8CVE-2023-2297: Profile Builder Insecure Password Reset Mechanism
CVE-2023-2297 - 9.8CVE-2021-24527: Profile Builder <= 3.4.8 Admin Access
CVE-2021-24527 - 9.8Profile Builder Authentication Bypass
- 8.8CVE-2021-36915: Profile Builder CSRF
CVE-2021-36915 - 8.8Profile Builder/Profile Builder Pro <= 3.3.2 Blind SQL Injection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C