dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12492

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Sensitive Information Exposure in all versions up to, and including, 2.11.0 via the ajax_get_members function. This is due to the use of a predictable low-entropy token (5 hex characters derived from md5 of post ID) to identify member directories and insufficient authorization checks on the unauthenticated AJAX endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including usernames, display names, user roles (including administrator accounts), profile URLs, and user IDs by enumerating predictable directory_id values or brute-forcing the small 16^5 token space.

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 plugin's ajax_get_members AJAX endpoint uses a weak 5-character hex token (16^5 = ~1M combinations) derived from md5 of post ID to identify member directories, combined with missing authorization checks. Unauthenticated attackers can enumerate valid tokens to extract usernames, display names, user roles, profile URLs, and user IDs.

MitigationUpdate Ultimate Member to version 2.11.1 or later which patches the predictable token and adds proper authorization. Alternatively, temporarily restrict access to the ajax_get_members endpoint via web server rules until patched.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check if Ultimate Member plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ultimate Member' in the list. Note the version number displayed.
    Affected if Ultimate Member plugin is installed and the version is below 2.11.1 (or if version cannot be determined)
  2. Verify ajax_get_members endpoint is accessible
    Send a request to your site's wp-admin/admin-ajax.php with action=ajax_get_members (no token required for detection of exposure). A 200 response indicates the endpoint is reachable.
    Affected if The endpoint responds to unauthenticated requests without requiring authorization
  3. Check if token generation is predictable
    Create multiple posts (member directories), then examine the token pattern in the HTML source of those pages. Look for a 5-character hex string in data-key attributes or similar. Compare tokens against md5(post_id) to confirm the weak derivation pattern.
    Affected if Tokens are 5-character hex strings and can be derived from post IDs using md5 truncation
  4. Confirm missing authorization on the endpoint
    Make an unauthenticated AJAX request to ajax_get_members with a guessed/derived token and observe if user data is returned.
    Affected if The endpoint returns member data (usernames, roles, profile URLs) without requiring authentication or valid authorization

Your environment is affected if the Ultimate Member plugin version is below 2.11.1 and the ajax_get_members endpoint is accessible to unauthenticated users with a predictable 5-character hex token derived from post IDs.

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 to version 2.11.1 or later which patches the predictable token and adds proper authorization. Alternatively, temporarily restrict access to the ajax_get_members endpoint via web server rules until patched.

Recommended fix Moderate confidence

Latest version greater than 2.11.0 (check WordPress plugin repository for current stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Ultimate Member plugin
  4. Check if current version is 2.11.0 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Verify update completed successfully
  7. Test that the Ultimate Member functionality works correctly after update
Caveat Review plugin changelog for any changes that may affect site functionality before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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