CVE-2026-7761
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 · uneditedThe Ultimate Member plugin for WordPress is vulnerable to Account Takeover via Password Reset Link Disclosure in all versions up to and including 2.11.4. This is due to a chain of three logic bugs: (1) an MD5 hash fallback in get_directory_by_hash() that allows any post to be used as a member directory by computing SUBSTRING(MD5(post_id), 11, 5), (2) a strstr() parsing logic flaw in post_data() that allows bypassing WordPress's protected meta key restrictions by placing '_um_' anywhere in the meta key name rather than at the start, and (3) missing field name validation in build_user_card_data() that allows arbitrary field names including 'password_reset_link' to be passed to um_filtered_value(). This makes it possible for authenticated attackers with Contributor-level access and above to create a malicious post via XMLRPC with crafted meta fields, use the MD5 fallback to point the member directory AJAX handler to their post, inject 'password_reset_link' into the tagline_fields configuration, and leak live password reset URLs for all users in the member directory response, including administrators.
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 confidenceThe Ultimate Member plugin versions up to 2.11.4 contain a critical account takeover vulnerability requiring three chained logic flaws. An authenticated Contributor+ attacker can craft a malicious post via XMLRPC with specially formed meta fields, exploit an MD5 hash fallback to redirect the member directory handler, bypass WordPress protected meta key restrictions via strstr() manipulation, and inject 'password_reset_link' into user card data to exfiltrate live password reset URLs for all users including administrators.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ultimate Member plugin versionCheck the installed Ultimate Member plugin version in WordPress under Plugins > Installed Plugins, or inspect the plugin header in /wp-content/plugins/ultimate-member/version.php or the main plugin fileAffected if Version is 2.11.4 or earlier (no fixed version is installed)
-
Verify XMLRPC is enabledAttempt to access /xmlrpc.php directly; or check WordPress settings under Settings > Writing > XML-RPC; or query the XMLRPC endpoint with a simple system.listMethods requestAffected if XMLRPC responds and is accessible (required vector for the attack)
-
Check for Contributor-level or higher usersNavigate to Users > All Users in WordPress admin and review user roles; or query wp_users and wp_usermeta tables for users with role capability levels >= ContributorAffected if Any user account with Contributor, Author, Editor, or Administrator role exists (attacker needs Contributor+ access)
-
Inspect directory handler configurationReview Ultimate Member settings for member directory functionality; check theme templates for calls to get_directory_by_hash() or related directory rendering functionsAffected if Member directory feature is active and uses the vulnerable hash-based handler
If Ultimate Member version is 2.11.4 or earlier, XMLRPC is enabled, and any Contributor+ user account exists, the environment is vulnerable to CVE-2026-7761.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Ultimate Member version 2.11.5 or later which patches all three logic flaws in get_directory_by_hash(), post_data(), and build_user_card_data(). Until patched, disable XMLRPC if not needed and restrict contributor-level user capabilities.
Ultimate Member plugin version 2.11.5 or later
- Upgrade the Ultimate Member WordPress plugin to version 2.11.5 or later
- After upgrading, verify the fix by checking that password_reset_link is no longer accessible through user metadata
- Review user accounts with Contributor-level or higher access to ensure no malicious posts were created during the vulnerability window
- If compromise is suspected, audit the wp_posts table for posts with crafted _um_ meta fields containing password_reset_link
- Consider forcing password reset for administrator accounts if evidence of exploitation exists
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7761 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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