Live › vulnerability › CVE-2026-107748
Go to dashboardThe User Profile Builder WordPress plugin does not sanitize the display_name field, so a logged-in subscriber can store a script that runs in the browser of anyone who views the injected page. The payload persists in the comment author field even after the display name is changed.
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 version 4.0.3 or earlier where subscriber-level or higher accounts can register or log in. Sites that do not allow public or subscriber registration and do not use this plugin can skip it.
No product ranges from the sources yet.
wp plugin get profile-builder --field=version4.0.3 once the vendor publishes one (unknown: fixed version not stated in the sources)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 the 'display_name' parameter in all versions up to, and including, 4.0.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload persists in wp_comments.comment_author independently of the user account, so removing or changing the attacker's display name after the comment is posted does not neutralize the stored script.
This page as .md · .json · in your agent: get_signal("CVE-2026-107748")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.