CVE-2026-106025: Cargo Shipping Location for WooCommerce (WordPress plugin) · Improper Access Control
Affects Cargo Shipping Location for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.0 when convenient.
Data as of 10 Nov 2026, 08:36 UTC
Thin evidence
One scorer or none| CNA (WPScan) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 6.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Cargo Shipping Location for WooCommerce (WordPress plugin) to 6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cargo Shipping Location for WooCommerce | Affected
| Fixed in
|
AI-suggested
Upgrade the Cargo Shipping Location for WooCommerce plugin to version 6.0 or later, where this vulnerability is fixed. No other mitigation is indicated or required.
Description
CVE-2026-106025 is a vulnerability in the Cargo Shipping Location for WooCommerce WordPress plugin versions 4.0.0 up to but not including 6.0. It allows unauthenticated users to access a REST API endpoint that updates order shipment statuses without proper authorization checks. This improper access control enables attackers to manipulate order statuses and shipment metadata. The issue is fixed in version 6.0.