dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31641

HIGH · 8.5 CVSS v3.1 Published 2025-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in LambertGroup UberSlider uber-classic allows SQL Injection.This issue affects UberSlider: from n/a through < 2.6.

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 · moderate confidence

SQL injection vulnerability in UberSlider uber-classic plugin allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade UberSlider to version 2.6 or later to obtain the patched version. If immediate upgrade is not feasible, implement parameterized queries or robust input validation/sanitization on all database interactions as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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. Locate the UberSlider uber-classic plugin installation
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'uberslider-pro' or similar, or access it via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder 'uberslider-pro' or 'uber-slider' exists in the plugins directory
  2. Determine the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find UberSlider uber-classic, and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually uberslider.php or similar) and look for the 'Version' header in the plugin comment block
    Affected if The version number is present and is below 2.6 (e.g., 2.5.x, 2.0.x, 1.x)
  3. Verify the plugin is active
    In WordPress admin, check the Plugins list and confirm whether UberSlider uber-classic is activated
    Affected if The plugin shows as 'Active' in the WordPress plugin list
  4. Confirm the vulnerability scope
    This SQL injection vulnerability requires user-supplied input to reach database queries unsanitized. Check if the plugin's frontend or admin features that accept user input (such as slider shortcodes, AJAX endpoints, or parameter inputs) are accessible on your site
    Affected if The plugin is active and its input-handling features are accessible to users or visitors

You are affected if UberSlider uber-classic is installed, active, and the installed version is below 2.6, exposing unsanitized database input fields.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade UberSlider to version 2.6 or later to obtain the patched version. If immediate upgrade is not feasible, implement parameterized queries or robust input validation/sanitization on all database interactions as a compensating control.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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