Live › vulnerability › CVE-2026-100186
Go to dashboardThe User Profile Builder WordPress plugin, up to and including 4.0.3, does not sanitize the First Name field on registration. An unauthenticated attacker can store a script there that runs in the browser of any user who opens an affected page.
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 up to and including 4.0.3 with the Email Confirmation feature enabled are exposed, since registration input is stored and rendered to visitors. Sites with the plugin absent or on a later version, or with Email Confirmation off, can skip it.
No product ranges from the sources yet.
4.0.3 are affected.4.0.3; the sources do not name the fixed version, so check the plugin changelog.Each 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 Stored Cross-Site Scripting via First Name Field in all versions up to, and including, 4.0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the Email Confirmation feature is enabled in Profile Builder.
This page as .md · .json · in your agent: get_signal("CVE-2026-100186")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.