CVE-2025-31397
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in smartcms Bus Ticket Booking with Seat Reservation for WooCommerce scw-bus-seat-reservation allows SQL Injection.This issue affects Bus Ticket Booking with Seat Reservation for WooCommerce: from n/a through <= 1.7.
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 confidenceSQL injection vulnerability in the Bus Ticket Booking with Seat Reservation for WooCommerce plugin (scw-bus-seat-reservation) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling complete database compromise including theft of sensitive customer and order data.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin > Plugins and confirm 'Bus Ticket Booking with Seat Reservation for WooCommerce' (scw-bus-seat-reservation) is listed as installedAffected if The plugin appears in the installed plugins list and is activated
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > click the plugin name to view details, or inspect the plugin main PHP file header for the 'Version' fieldAffected if The installed version is unknown, unpatched, or falls within a vulnerable version range (contact vendor for specific affected versions)
-
Check plugin directory structureAccess the WordPress wp-content/plugins directory via file manager or FTP, locate the scw-bus-seat-reservation folder, and verify the main plugin file existsAffected if The plugin files are present on the server indicating the plugin is deployed
-
Review web server logs for SQL injection attemptsExamine Apache/Nginx access logs and error logs for requests to plugin endpoints containing SQL injection payloads (e.g., single quotes, UNION SELECT, OR 1=1 patterns in URL parameters)Affected if Recent logs show suspicious SQL-like patterns in requests targeting the scw-bus-seat-reservation plugin endpoints
-
Check for unexpected database behaviorReview WooCommerce database tables (wp_posts, wp_postmeta, wp_woocommerce_session_notes) for unexpected modifications or unfamiliar data entries that may indicate prior exploitationAffected if Database contains suspicious queries, unknown records, or evidence of unauthorized access to customer/order tables
If the plugin is installed and active, and particularly if SQL injection patterns appear in server logs or suspicious database activity is observed, the environment is likely affected and should be investigated further.
Generated from the published advisory. Verify against your own configuration.
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 dataContact the vendor for an emergency patch; if unavailable, consider disabling the plugin, deploying a WAF rule to block SQL injection payloads, or implementing input validation at the web application layer as a temporary workaround.
- Consultation4.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31397 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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