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

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Cargo Shipping Location for WooCommerce: ≥ 4.0.0; < 6.0 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CVSS 3.1: 5.3 (medium); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N; source: CNA: WPScan

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-284

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/07169e63-f50e-4e9e-a5c0-1f9e57a3c0dd/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/07169e63-f50e-4e9e-a5c0-1f9e57a3c0dd/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-106025; retrieved 2026-11-10; source updated 2026-11-10

Revision: fc857484bdded319e5d4f6608f8d84c288e32168e3826b13b2c40e1a443b3a3c

Canonical: https://y2.dev/cve/CVE-2026-106025

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.