CVE-2026-121790: CWILL (Formerly ParcelPanel) <= 4.6.2 - Unauthenticated Stored Cross-Site Scripting via 'courier_code' and 'tracking_number' Parameters via REST Auth Bypass
The CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[].couriercode, data[].trackingnumber (plus ppsign 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 parcelpanelapikey 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 ppsign, which PHP's loose == operator coerces to true when compared against the non-empty md5 hex string.
Affected Software
Event History
Frequently Asked Questions
Which sites are exposed to unauthenticated exploitation?
Sites running CWILL/ParcelPanel version 4.6.2 or earlier are exposed once the parcelpanel_api_key WordPress option is non-empty. This occurs automatically after an administrator opens or connects the ParcelPanel admin page.
What does an attacker need to bypass the REST access check?
No account or user interaction is required. The attacker can supply a JSON boolean true as pp_sign, which bypasses the comparison when the API key option contains a non-empty value.
What can an attacker do after exploiting the issue?
An attacker can store arbitrary web script through the courier_code and tracking_number parameters. The script executes when a user visits a page containing the injected content, potentially exposing information available to that user or performing actions in that user's browser context.
How can I determine whether my site may be affected?
Check whether the installed plugin version is 4.6.2 or earlier and whether the parcelpanel_api_key WordPress option is populated. A populated option indicates that the REST authentication bypass condition is reachable.