dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11766

HIGH · 8.0 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 WordPress plugin before 2.12.0 does not properly sanitise and escape the value of custom textarea profile fields before outputting it on user profiles, allowing authenticated users with Subscriber-level access and above to store JavaScript that executes when any user, including an administrator, views the affected profile.

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 before 2.12.0 fails to properly sanitize and escape values in custom textarea profile fields, allowing authenticated Subscriber-level users to inject malicious JavaScript that executes in the browsers of anyone viewing the affected user profile.

MitigationUpdate Ultimate Member plugin to version 2.12.0 or later to obtain the patched version that properly escapes output from custom profile fields.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Ultimate Member plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ultimate Member' in the list. Note the installed version number displayed.
    Affected if The plugin is present in the plugins list
  2. Check Ultimate Member version against vulnerability range
    Compare the installed version from the plugins page to the affected range: versions before 2.12.0 are vulnerable. The plugin version is typically displayed alongside the plugin name in the WordPress plugins list.
    Affected if Installed version is lower than 2.12.0 (e.g., 2.11.0, 2.10.0, etc.)
  3. Identify custom profile field configuration
    Navigate to Ultimate Member > Forms in the WordPress admin. Review any registered profile forms and look for custom profile fields, specifically textarea-type fields that may have been added by administrators.
    Affected if Custom textarea profile fields exist in the Ultimate Member form settings
  4. Check for subscriber-level user accounts
    In WordPress admin, go to Users and review the user list. Look for users with the Subscriber role, or query the wp_usermeta table for users where meta_value contains 'a:1:{s:10:"subscriber";'
    Affected if There are users assigned the Subscriber role in WordPress
  5. Verify profile forms allow public profile viewing
    Navigate to Ultimate Member > Settings > Access and check if profile viewing is enabled. Also check if profile fields are set to display on the frontend member directory or individual profile pages.
    Affected if Profile viewing is enabled and custom profile fields are configured to display publicly

You are affected if Ultimate Member plugin version is below 2.12.0 AND custom textarea profile fields exist AND are configured to display on user profiles that are viewable by subscriber-level users or other site visitors.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ultimate Member plugin to version 2.12.0 or later to obtain the patched version that properly escapes output from custom profile fields.

Recommended fix High confidence

Ultimate Member 2.12.0 or later

  1. 1. Create a full backup of the WordPress site (database and files) before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the Ultimate Member plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.12.0 or later
  5. 5. Alternatively, upload Ultimate Member version 2.12.0 or newer via Plugins > Add New > Upload Plugin
  6. 6. Alternatively, run: wp plugin update ultimate-member --version=2.12.0 (or later) via WP-CLI
  7. 7. Verify the installed version is 2.12.0 or higher in Plugins > Installed Plugins
  8. 8. Clear any caching plugins if present
Caveat Minor plugin point releases typically do not introduce breaking changes; always test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11766 — 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-11766 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