CVE-2026-85680: Ultimate Member WordPress plugin stored XSS in profile page title

CVE-2026-85680 · Severity: high · CVSS 8.8 · Published 2026-09-19

The Ultimate Member WordPress plugin allows unauthenticated users to register accounts and inject malicious JavaScript into their profile names. When administrators or other visitors view an attacker's profile, the stored JavaScript executes in their browsers, potentially compromising their accounts or stealing sensitive data. This affects all installations of the plugin before version 2.13.1.

Technologies: Ultimate Member. Vendors: Ultimate Member.

Quick answers

Is CVE-2026-85680 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-85680 being exploited in the wild.
How severe is CVE-2026-85680?
High severity, with a CVSS score of 8.8, published 19 September 2026.
Which products and versions are affected?
Ultimate Member before 2.13.1.
Is there a fix for CVE-2026-85680?
A patch was published on 2026-09-XX: Fixed in version 2.13.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85680 attacked?
It is attacked over the network.
Am I affected by CVE-2026-85680?
Check whether you run Ultimate Member at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The plugin fails to properly escape user-supplied profile names before outputting them in the page title and performs HTML entity decoding after its own sanitization, allowing stored XSS. An unauthenticated attacker who registers an account can inject JavaScript payloads that persist in the database and execute when any visitor, including administrators, views the profile. The vulnerability is triggered via profile page rendering and requires only account registration.

Affected products

  • Ultimate Member Ultimate Member before 2.13.1

Timeline

  • 2026-09-17: disclosed: Publicly disclosed vulnerability
  • 2026-09-XX: patched: Fixed in version 2.13.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.