Summary
CVE-2026-15826 is a critical authentication bypass vulnerability in the Profile Builder Pro (User Profile Builder) WordPress plugin by Cozmoslabs, affecting all versions up to and including 3.16.4. A type-confusion flaw in the plugin’s login-handling code allows unauthenticated attackers to obtain an autologin session as the site’s Administrator account. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: the plugin’s
wppb_log_in_user()function passes the return value ofwp_insert_user()throughabsint()before callingis_wp_error()to check for registration failures. - Trigger condition: submitting a front-end registration request with a username 61–70 characters long causes WordPress core to reject the registration and return a
WP_Errorobject instead of a numeric user ID. absint()coerces thatWP_Errorobject into the integer1, which the plugin then treats as a valid user ID — user ID 1 is typically the original site Administrator.- The plugin proceeds to generate and use an autologin nonce for that coerced ID, authenticating the requester as that user.
- Attack vector: network, no authentication or user interaction required, executed via a standard front-end registration form submission.
- Impact: full administrative account takeover, granting confidentiality, integrity, and availability impact consistent with complete site compromise.
Affected software
- Profile Builder Pro / User Profile Builder (WordPress plugin, Cozmoslabs) — all versions up to and including 3.16.4.
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: upgrade Profile Builder Pro / User Profile Builder to a version newer than 3.16.4 that includes the vendor’s fix to the
wppb_log_in_user()validation logic. - If patching cannot be applied immediately: disable or restrict access to the plugin’s front-end user registration form, or place a web application firewall rule in front of the registration endpoint to block usernames in the 61–70 character range.
- After remediation: review WordPress user accounts and administrator activity logs for signs of unauthorized login or account creation predating the patch.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/wp-content/plugins/profile-builder-pro/

