dbcve.org
Ultimate MemberWordPress extension · Ultimatemember

CVE-2025-0308

HIGH · 7.5 CVSS v3.1 Published 2025-01-18
Fix available
A fix is available. Upgrade to 2.9.2 or later.
See remediation →
84/100
Remediation priority · High
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 time-based SQL Injection via the search parameter in all versions up to, and including, 2.9.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 is vulnerable to time-based SQL injection via the search parameter in versions up to 2.9.1. The vulnerability stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the underlying SQL query, allowing unauthenticated attackers to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate the Ultimate Member plugin to version 2.9.2 or later, which contains the patched code with proper parameter escaping and prepared SQL statements. If immediate update is not possible, consider temporarily disabling the affected search functionality or implementing a WAF rule to block SQL injection attempts.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 > Plugins and confirm Ultimate Member appears in the installed plugins list, or check the filesystem at /wp-content/plugins/ultimate-member/
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    In WordPress Admin > Plugins, find Ultimate Member and view the version number displayed under the plugin name, or read the main plugin file header at /wp-content/plugins/ultimate-member/ultimate-member.php for the Version constant
    Affected if The version is below 2.9.2 (e.g., 2.9.1, 2.9.0, earlier versions)
  3. Confirm search functionality is accessible
    Visit the frontend of the site and locate the Ultimate Member search form (typically at /members/ or a page with UM search shortcode), or inspect the site's publicly accessible endpoints that handle the search parameter
    Affected if The search feature is enabled and reachable without authentication
  4. Inspect HTTP traffic for search parameter handling
    Send a test request to a search endpoint (such as ?um_search= or the site's member search URL) and verify the parameter is passed to the backend database query without visible sanitization in server response headers
    Affected if The search parameter is processed and reflected in SQL queries without prepared statements

If Ultimate Member version is below 2.9.2 and the search feature is publicly accessible, the environment is vulnerable to CVE-2025-0308 SQL injection.

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, which contains the patched code with proper parameter escaping and prepared SQL statements. If immediate update is not possible, consider temporarily disabling the affected search functionality or implementing a WAF rule to block SQL injection attempts.

Recommended fix High confidence

Ultimate Member version 2.9.2

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate the Ultimate Member plugin in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.9.2
  5. Verify the plugin is running version 2.9.2 or later under Plugins > Installed Plugins
  6. Test critical member registration, profile display, and member directory functionality to ensure the update did not break existing features

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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