SQL Injection in Cargo Shipping Location for WooCommerce (CVE-2026-54815)
Summary
SQL injection in Cargo Shipping Location for WooCommerce (CVE-2026-54815). Confidential information can be exposed externally.
Original description
The description as published by the source.
Improper 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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54815 has been found in Cargo Shipping Location for WooCommerce.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cargo Shipping Location for WooCommerce CVE-2026-54815" on the vendor's site.
CVE-2026-54815 (Cargo Shipping Location for WooCommerce) — CWE-89 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in Cargo Shipping Location for WooCommerce.
Check the vendor advisory for the affected versions of Cargo Shipping Location for WooCommerce.
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cargo Shipping Location for WooCommerce を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web audit@patchstack.com
- web github.com