dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8489

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 'about_me' parameter in all versions up to, and including, 2.11.4 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Ultimate Member WordPress plugin fails to properly sanitize the 'about_me' user profile field on input and escape it on output. Attackers with basic subscriber-level accounts can inject malicious JavaScript payloads into this field, which are then stored and executed in the browsers of any user viewing the injected profile.

MitigationUpdate the Ultimate Member plugin to version 2.11.5 or later which contains proper input sanitization and output escaping for the 'about_me' parameter. Review existing user profiles for any injected malicious scripts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ultimate Member plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Ultimate Member'. Note the installed version number.
    Affected if The plugin is installed and the version is below 2.11.5 or the version cannot be determined
  2. Verify the 'about_me' field is enabled
    Go to Ultimate Member > Forms > Profile Forms (or similar form builder). Check if the 'About Me' field is included in any active profile form.
    Affected if The 'about_me' field exists in an active profile form that regular users can access
  3. Inspect existing user profiles for malicious content
    Navigate to Users > All Users in WordPress admin. View profile pages of users with subscriber-level roles. Check the 'About Me' or bio section for suspicious script tags, event handlers (onload, onerror, etc.), or encoded payloads.
    Affected if Any user profile contains JavaScript code in the about_me field that was not intentionally added by an administrator
  4. Check form submission settings
    Go to Ultimate Member > Settings > Forms. Verify if basic subscriber-role users can submit or edit their profile and access the about_me field.
    Affected if Subscriber-level accounts have permission to edit their profile and access the about_me field

A user is affected if they have Ultimate Member plugin installed with version below 2.11.5, the about_me field is enabled in an accessible profile form, and subscriber-level users can edit that field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Ultimate Member plugin to version 2.11.5 or later which contains proper input sanitization and output escaping for the 'about_me' parameter. Review existing user profiles for any injected malicious scripts.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8489 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data