Read the docs

Stored cross-site scripting in WP User Manager via display_name

Priority LOW 28CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

WP User Manager for WordPress is affected in all versions up to and including 2.10.2. Insufficient input sanitization and output escaping of the display_name user field allow stored cross-site scripting (CWE-79). An authenticated attacker with subscriber-level access or above can inject web scripts that run in a user's browser when that user opens an affected page. The WordPress core REST users endpoint stores the value without the plugin's sanitizer, so the plugin's save-time sanitization does not mitigate the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00335 27th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
WP User ManagerWP User Manager – Registration Form, Login Form, User Profile Builder & Member Directoryup to 2.10.2—No fix listedCNA
  • WP User Manager – Registration Form, Login Form, User Profile Builder & Member Directory VendorWP User Manager Affected up to 2.10.2 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for WP User Manager.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Timeline

  1. 2026-11-06 Threatist record created from CVE-2026-120550
  2. 2026-11-06 Alias added: GHSA-q737-h7j9-qw8g
  3. 2026-11-06 CISA SSVC decision points changed
  4. 2026-11-06 Priority changed: MEDIUM → LOW

References

  • TI-2025-37611 WordPress WP User Manager plugin <= 2.9.12 - PHP Object Injection vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2026-08157 WP User Manager <= 2.9.17 - Unauthenticated Path Traversal to Local File Inclusion via 'tab' Query Parameter CVSS 3.1HIGH 7.5
  • TI-2026-36675 WordPress WP User Manager plugin <= 2.9.16 - Arbitrary File Deletion vulnerability CVSS 3.1CRITICAL 9.9
  • TI-2021-06937 WP User Manager < 2.6.3 - Arbitrary User Password Reset to Account Compromise CVSS 3.1HIGH 7.5
  • TI-2026-67832 Improper access control in WP User Manager WordPress plugin CVSS 3.1MEDIUM 6.5
  • TI-2025-12183 WP User Manager <= 2.9.12 - Authenticated (Subscriber+) Arbitrary File Deletion via 'current_user_avatar' Parameter CVSS 3.1MEDIUM 6.8
See all 15 →

Sources