dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-25150

CRITICAL · 9.3 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stylemix uListing ulisting allows Blind SQL Injection.This issue affects uListing: from n/a through <= 2.1.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

A blind SQL injection vulnerability exists in the Stylemix uListing WordPress plugin (versions up to 2.1.6). The vulnerability stems from improper neutralization of special elements in SQL commands, allowing authenticated or unauthenticated attackers to inject malicious SQL queries via vulnerable input parameters. Blind SQL injection means attackers infer information from application behavior differences rather than seeing direct output.

MitigationUpdate uListing to the latest patched version. If no patch is available, identify and sanitize all user-supplied input in SQL queries, implement prepared statements/parameterized queries, and consider temporarily disabling the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm uListing plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'uListing' in the list, or inspect the plugin header file (typically in /wp-content/plugins/ulisting/) for the version comment
    Affected if uListing plugin is present on the WordPress site
  2. Identify installed uListing version
    Read the version number from the plugin's main file (usually ulisting.php) header or from the Plugins page in WordPress admin
    Affected if Version is 2.1.6 or any earlier version (the vulnerability affects versions up to 2.1.6)
  3. Verify plugin is active
    Check the Plugins page in WordPress admin to confirm uListing is activated, or query the wp_options table for option_name='active_plugins'
    Affected if Plugin is active and handling requests
  4. Determine if public listing features are accessible
    Visit the site's frontend listing pages, search pages, or submission forms that use uListing functionality. Common endpoints include /ulisting/, /mylisting/, or custom shortcodes like [ulisting]
    Affected if Public-facing uListing pages accept user input and are accessible without authentication (the CVE notes unauthenticated attackers can exploit this)
  5. Inspect application logs for anomalous database patterns
    Review web server access logs and WordPress debug logs (if enabled) for unusual query patterns, excessive database errors, or repeated similar requests to uListing endpoints that may indicate injection testing
    Affected if Logs show repeated SQL syntax errors or unusual query patterns targeting uListing parameters

If uListing version 2.1.6 or lower is installed, active, and its features are publicly accessible, the environment is likely affected by this blind SQL injection vulnerability.

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 uListing to the latest patched version. If no patch is available, identify and sanitize all user-supplied input in SQL queries, implement prepared statements/parameterized queries, and consider temporarily disabling the plugin until a fix is released.

Recommended fix Moderate confidence

Latest version > 2.1.6 (contact Stylemix support or check their official channels for the specific fixed release number)

  1. 1. Update the Stylemix uListing WordPress plugin to the latest available version from the WordPress plugin repository or Stylemix website.
  2. 2. After updating, verify that the plugin version is greater than 2.1.6.
  3. 3. Test critical user-facing functionality (listing creation, search, user submission forms) to ensure the update did not introduce regressions.
  4. 4. Review activity logs for any signs of exploitation attempts prior to the patch.
Caveat Minor or patch updates typically have no breaking changes; verify plugin compatibility with your WordPress version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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