---
id: "CVE-2026-107748"
kind: "vulnerability"
aliases: ["CVE-2026-107748"]
title: "WordPress User Profile Builder plugin: stored XSS via display_name up to 4.0.3"
severity: "medium"
cvss: 6.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "wordpress", "wordpress-plugins"]
not_affected_if: ["plugin-not-installed", "plugin-updated", "registration-disabled"]
published_at: "2026-10-16T06:17:05+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:59:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107748", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WordPress User Profile Builder plugin: stored XSS via display_name up to 4.0.3

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of User Profile Builder in the WordPress plugins screen or with `wp plugin get profile-builder --field=version`
- Look for stored comments or pages containing script tags in comment_author in the wp_comments table

## Fix

- Update User Profile Builder to a version later than `4.0.3` once the vendor publishes one (unknown: fixed version not stated in the sources)
- Remove any injected script from wp_comments.comment_author after updating

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-107748

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_