dbcve.org
Ultimate MemberWordPress extension · Ultimatemember

CVE-2025-0318

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-18
Fix available
A fix is available. Upgrade to 2.9.2 or later.
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 Information Exposure in all versions up to, and including, 2.9.1 through different error messages in the responses. This makes it possible for unauthenticated attackers to exfiltrate data from wp_usermeta table.

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 versions up to 2.9.1 are vulnerable to information disclosure through verbose error messages that leak data from the wp_usermeta table. Unauthenticated attackers can exploit this by triggering different error responses to inferentially extract user metadata, a technique common in error-based data exfiltration.

MitigationUpdate the Ultimate Member plugin to version 2.9.2 or later. If immediate update is not possible, consider disabling the plugin or implementing WAF rules to detect and block anomalous requests targeting user metadata endpoints.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ultimate MemberWordPress extension
Affected:< 2.9.2

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. Verify Ultimate Member plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm Ultimate Member appears in the installed plugins list, or check the plugin files in /wp-content/plugins/ultimate-member/ for the main plugin file
    Affected if Ultimate Member plugin is present on the WordPress site
  2. Determine installed Ultimate Member version
    In WordPress admin > Plugins, find Ultimate Member and view the version number displayed under the plugin name, or inspect the main plugin file header in /wp-content/plugins/ultimate-member/ultimate-member.php for the 'Version' field
    Affected if The installed version is 2.9.1 or lower (any version below 2.9.2)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Ultimate Member plugin shows as 'Active' rather than 'Inactive'
    Affected if The plugin is active and the version is below 2.9.2
  4. Verify site exposes verbose error responses
    Without exploiting, observe whether the site returns detailed PHP or database error messages when malformed requests are made to user-related endpoints, or check if WP_DEBUG is enabled in wp-config.php
    Affected if Detailed error messages are displayed and the plugin version is below 2.9.2

A site is affected if the Ultimate Member plugin version is below 2.9.2, is active, and the WordPress environment displays verbose error messages that could leak wp_usermeta table data to unauthenticated attackers.

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
Upgrade available Upgrade to 2.9.2 or later
Fixed in 2.9.2
Interim mitigation

Update the Ultimate Member plugin to version 2.9.2 or later. If immediate update is not possible, consider disabling the plugin or implementing WAF rules to detect and block anomalous requests targeting user metadata endpoints.

Recommended fix High confidence

2.9.2

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Ultimate Member in the plugin list
  4. If update is available, click 'Update Now' to upgrade to version 2.9.2 or later
  5. Verify the plugin version shows 2.9.2 or higher after update
  6. Test user registration, login, and profile functionality to ensure the site works correctly

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

Fix this in Ultimate Member Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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