CVE-2025-31403
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 shiptrack Booking Calendar and Notification booking-calendar-and-notification allows Blind SQL Injection.This issue affects Booking Calendar and Notification: from n/a through <= 4.0.3.
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 confidenceA blind SQL injection vulnerability exists in the shiptrack Booking Calendar and Notification plugin (versions <= 4.0.3). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized user input, potentially enabling data exfiltration from the database or further compromise of the affected system.
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.
-
Locate the shiptrack Booking Calendar pluginAccess your WordPress admin dashboard, navigate to Plugins, and search for 'shiptrack Booking Calendar and Notification' in the installed plugins list. Note the version number displayed next to the plugin name.Affected if The plugin is installed and the version shown is 4.0.3 or lower
-
Verify the plugin files existCheck the wp-content/plugins directory for a folder named 'shiptrack-booking-calendar' or similar. Examine the main plugin file (usually named main.php, shiptrack.php, or index.php) within that folder for the version declaration.Affected if The plugin files exist and the hardcoded version in the plugin header reads 4.0.3 or below
-
Confirm booking calendar functionality is activeVisit the frontend of your WordPress site where the booking calendar shortcode or widget is embedded. Common shortcode patterns include [shiptrack_booking], [shiptrack-calendar], or similar. Verify the calendar form loads and accepts user input.Affected if The booking calendar form is rendered and functional on any public-facing page, allowing users to submit booking requests with input fields
-
Identify exposed booking input parametersInspect the HTML source of an active booking calendar page. Look for form fields that submit to the backend (typically POST requests to admin-ajax.php or the plugin's endpoint). Common field names include booking_date, customer_name, email, or similar booking-related parameters.Affected if Form fields are present and submit user-provided data directly to the plugin's backend processing without obvious sanitization indicators in the code
You are affected if the shiptrack Booking Calendar and Notification plugin is installed at version 4.0.3 or lower and the booking calendar form is accessible to users, as the unsanitized user input in this functionality enables the blind SQL injection.
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 dataUpgrade to a patched version of the Booking Calendar and Notification plugin as soon as one becomes available. If no patch is available, disable the plugin until a fix is released.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31403 — 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-31403 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