CVE-2026-96270: Ultimate Member (WordPress plugin) · Cross-site Scripting
Affects Ultimate Member (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ultimatememberUltimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, restrict administrative access to trusted personnel only and avoid opening suspicious user records. Implementing additional input sanitization or output escaping at the application or web server level may reduce risk.
Description
The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form_id' parameter in all versions up to, and including, 2.13.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is stored in the registering user's 'submitted' usermeta via update_user_meta() and is only triggered when an administrator opens the affected user record in the wp-admin Users modal, which inserts the unescaped output via jQuery .html().
References
- wordfence.com/threat-intel/vulnerabilities/id/5673f2b9-1c30-4ce0-8a8c-7580d0346cb9?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/um-short-functions.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/um-short-functions.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/admin/core/class-admin-builder.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/core/class-form.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/core/class-form.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/ultimate-member/tags/2.13.1/includes/core/class-user.php (opens in a new tab)
- github.com/ultimatemember/ultimatemember/releases/tag/2.14.0 (opens in a new tab)