CVE-2026-120550 · Package
NO FIX YET · SEE WHAT TO DO
The WP User Manager plugin for WordPress up to and including 2.10.2 does not sanitize the display name saved through the core REST users endpoint. An authenticated subscriber can store a script in their display name that runs in the browser of anyone who views the injected page.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running WP User Manager 2.10.2 or earlier where users can register or log in with a subscriber-level account. The flaw is reached through WordPress core's REST users endpoint, so the plugin's own front-end form sanitizer does not protect it. Sites with registration closed and no subscriber accounts are much less exposed.
Not affected if plugin-not-installed, registration-closed, version-above-2.10.2
Who cares self-hosted, wordpress, wp-user-manager
wp-content/plugins/wp-user-manager/2.10.2 (fixed version not stated in the sources)The WP User Manager – Registration Form, Login Form, User Profile Builder & Member Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name (REST users endpoint) -> wp_users.display_name' parameter in all versions up to, and including, 2.10.2 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 is stored via the WordPress core REST endpoint POST /wp-json/wp/v2/users/me, which bypasses the plugin's own wpum_sanitize_text sanitizer applied on its front-end account form, making the save-time sanitization ineffective as a mitigation.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.