CVE-2026-54815
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 Cargo RD Cargo Shipping Location for WooCommerce allows Blind SQL Injection. This issue affects Cargo Shipping Location for WooCommerce: from n/a through 5.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 confidenceA blind SQL injection vulnerability exists in the Cargo Shipping Location for WooCommerce plugin. Attackers can inject malicious SQL queries through unsanitized input parameters, potentially allowing extraction of sensitive database information or manipulation of data through boolean-based or time-based inference techniques.
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.
-
Confirm plugin installationNavigate to WordPress admin > Plugins and verify 'Cargo Shipping Location for WooCommerce' is installed and activeAffected if The plugin is installed and active in WordPress
-
Identify plugin versionIn Plugins list, click on the plugin to view version details, or check the plugin header in /wp-content/plugins/ directory for the 'Version' fieldAffected if Version is unknown or falls within an unpatched range (contact vendor for patch status)
-
Verify shipping location feature is in useCheck WooCommerce > Settings > Shipping for any configured Cargo Shipping Location zones or methods, or inspect database table options for 'woocommerce_cargo_shipping' related settingsAffected if Shipping location functionality is enabled or configured in WooCommerce
-
Inspect HTTP request handling for the vulnerable endpointIdentify forms or API endpoints handling shipping location input (check plugin PHP files for $_GET, $_POST, or $_REQUEST usage related to location parameters), then test by submitting SQL injection payloads in location fieldsAffected if User-supplied input in location fields is passed directly to SQL queries without prepare() or parameterized binding
-
Review plugin code for SQL injection vulnerabilitiesExamine plugin source files (typically in /wp-content/plugins/cargo-shipping-location-for-woocommerce/) for unsanitized SQL queries, specifically looking for $wpdb->prepare() absence in shipping location query functionsAffected if SQL queries use user input without $wpdb->prepare() or equivalent sanitization
If the plugin is active, the shipping location feature is in use, and user input reaches SQL queries without prepared statements, the environment is vulnerable to CVE-2026-54815
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 dataUpdate to a patched version of the plugin immediately. If no patch is available, disable the plugin or deploy WAF rules to block SQL injection attempts until a fix is released.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54815 — 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-2026-54815 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