dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-58951

CRITICAL · 9.3 CVSS v3.1 Published 2025-12-18
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 smartcms Advance Seat Reservation Management for WooCommerce scw-seat-reservation allows SQL Injection.This issue affects Advance Seat Reservation Management for WooCommerce: from n/a through <= 3.1.

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

SQL injection vulnerability in the WordPress plugin 'Advance Seat Reservation Management for WooCommerce' (scw-seat-reservation) up to version 3.1 allows attackers to inject malicious SQL queries through unsanitized input, potentially enabling unauthorized data access, modification, or deletion of database contents including customer reservations and user credentials.

MitigationUpdate to the patched version once released by the vendor; in the interim, restrict access to the plugin endpoints via WAF or access controls, and consider disabling the plugin if no immediate patch is available.

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 plugin is installed
    Check WordPress plugins directory for 'scw-seat-reservation' folder, or query the wp_plugins database table for plugin slug 'scw-seat-reservation'
    Affected if The plugin folder or database entry exists in the WordPress installation
  2. Check installed plugin version
    Inspect the plugin main file header (e.g., scw-seat-reservation.php) for the 'Version' tag, or query wp_options for option_name containing 'scw-seat-reservation' version
    Affected if The version is 3.1 or lower (including any version below the patched release)
  3. Verify plugin is active
    Query wp_options table for option_name='active_plugins' and check if 'scw-seat-reservation' appears in the serialized array, or check WordPress admin plugins list
    Affected if The plugin appears in the active plugins list and is enabled on the site
  4. Identify exposed endpoints
    Review plugin code for AJAX handlers (wp_ajax_*) or REST API routes (register_rest_route) that process user input, particularly search or filter parameters that may reach the database
    Affected if The plugin exposes any frontend-facing AJAX or REST endpoints that accept user-supplied input without sanitization

You are affected if the scw-seat-reservation plugin is installed, active, and running version 3.1 or lower on your WordPress site.

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

Update to the patched version once released by the vendor; in the interim, restrict access to the plugin endpoints via WAF or access controls, and consider disabling the plugin if no immediate patch is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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