Live › vulnerability › CVE-2026-109447
Go to dashboardThe User Profile Builder WordPress plugin up to and including 4.0.3 lets an unauthenticated visitor submit a role value during registration that is passed straight to the user role setter. A legacy form field named role can carry that value through email activation, letting the attacker become a full WordPress administrator.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running User Profile Builder at version 4.0.3 or older that have a public [wppb-register] form with open registration and email confirmation enabled. The risk is highest where a form field with meta-name role survived an earlier upgrade. Sites without the plugin, with registration closed, or without email confirmation are not exposed on the stated path.
No product ranges from the sources yet.
wp plugin get profile-builder --field=versionrole that was created before the 4.0.3 upgrade4.0.3 (exact fixed version unknown from sources)role from the registration formsEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-109447")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.