Skip to main content
CVE-2026-120550VulnerabilityPublished

The WP User Manager – Registration Form, Login Form, User Profile Builder & Member Directory plugin for WordPress is

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120550· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 6 Nov 2026, 13:48 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
wpusermanagerWP User Manager – Registration Form, Login Form, User Profile Builder & Member DirectoryAffected
  • <=2.10.2
Fixed in–

AI-suggested

Users should monitor the vendor advisory for updates. Until a fix is available, restricting user privileges and limiting access to trusted users may reduce risk. Because the vulnerability exploits the REST API endpoint, disabling or restricting REST API access for non-administrative users could mitigate exploitation.

Description

The WP User Manager plugin for WordPress up to version 2.10.2 contains a stored cross-site scripting (XSS) vulnerability via the 'name' parameter in the REST users endpoint. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises because the plugin's front-end sanitization is bypassed by using the WordPress core REST endpoint, making save-time sanitization ineffective.

References

Community reviews

Loading reviews…