User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor <= 4.0.3 - Authenticated (Author+) Limited Privilege Escalation via Gutenberg Block 'Assigned Role' Attribute
Impact
The User Profile Builder plugin for WordPress, versions up to 4.0.3, has a Limited Privilege Escalation vulnerability. Authenticated attackers with Author-level access can create new accounts with the Editor role. This is due to improper authorization of the Assigned Role attribute in the Gutenberg block.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
cozmoslabs · Wordfence
User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
1 range
cozmoslabs · Wordfence
User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 4.0.3
semver versions
Other versions: unaffected
Original source description
The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to Limited Privilege Escalation in all versions up to, and including, 4.0.3. This is due to the Gutenberg Register block passing the attacker-controlled Assigned Role attribute directly into the [wppb-register] shortcode without server-side authorization. The role guard in the form builder only downgrades roles that carry the manage_options or remove_users capability, leaving the Editor role and other privileged non-Administrator roles completely unrestricted. This makes it possible for authenticated attackers with Author-level access and above to create new WordPress accounts bearing the Editor role (or any other role that lacks the two guarded capabilities).
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-115807View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.