dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15290

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
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 No privileges Zero-click 6 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 – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to blind SQL Injection via the search parameter in all versions up to, and including, 2.10.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. This vulnerability was partially patched in version 2.9.2 when initially addressing CVE-2025-0308.

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.10.1 contain a blind SQL injection vulnerability in the search parameter. Due to insufficient input escaping and lack of prepared statements, unauthenticated attackers can append malicious SQL queries to extract sensitive data from the database.

MitigationUpdate to the latest plugin version after 2.10.1. As a temporary measure, consider deploying a WAF rule to block SQL injection patterns in the search parameter or disable the plugin if immediate patching is not possible.

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
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
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the ultimate-member folder, or query the wp_options table for the active_plugins option
    Affected if Ultimate Member plugin is not found in the WordPress installation
  2. Check installed Ultimate Member version
    In WordPress admin, go to Plugins > Installed Plugins and locate Ultimate Member to view the version number, or read the version from /wp-content/plugins/ultimate-member/readme.txt, or query the wp_options table for the option_name containing 'ultimate_member_version'
    Affected if The version is 2.10.1 or lower (any version up to and including 2.10.1)
  3. Confirm member directory search feature is enabled
    Navigate to Ultimate Member > Directories in WordPress admin, or inspect the wp_um_directory table in the database, or check if the shortcode [ultimatemember] or a directory page exists on the site
    Affected if A member directory with search functionality is publicly accessible (the plugin's search parameter is exposed)
  4. Inspect search parameter handling for SQL injection vulnerability
    Review the plugin source code in /wp-content/plugins/ultimate-member/core/um-query.php or similar files handling the search parameter, looking for direct use of $_GET['search'] or $_REQUEST['search'] without $wpdb->prepare() or esc_sql()
    Affected if The search parameter is used in SQL queries without proper preparation or escaping (vulnerable code pattern exists)

You are affected if Ultimate Member plugin version 2.10.1 or lower is installed and the member directory search feature is enabled, exposing the unauthenticated search parameter to potential 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest plugin version after 2.10.1. As a temporary measure, consider deploying a WAF rule to block SQL injection patterns in the search parameter or disable the plugin if immediate patching is not possible.

Recommended fix Moderate confidence

Ultimate Member 2.10.2 or latest stable release (verify current fixed version at wordpress.org/plugins/ultimate-member)

  1. Check the WordPress plugin repository or Ultimate Member's official release notes for version 2.10.2 or later to confirm the full security fix
  2. Backup your WordPress database before performing any plugin update
  3. Update the Ultimate Member plugin to the latest available version (2.10.2 or later) via WordPress admin dashboard or FTP
  4. Verify the update was successful and test that the member directory and search functionality work correctly
  5. Monitor for any unusual database activity or errors in logs following the update
Caveat Standard minor plugin updates rarely introduce breaking changes, but test in staging if you have custom Ultimate Member templates or extensions

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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