CVE-2026-39540
Description
Unauthenticated stored XSS in Shipment Tracker for Woocommerce <=1.5.3.2 allows arbitrary script injection via subscriber role.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated stored XSS in Shipment Tracker for Woocommerce <=1.5.3.2 allows arbitrary script injection via subscriber role.
Vulnerability
The Shipment Tracker for Woocommerce plugin for WordPress versions 1.5.3.2 and earlier contains a stored Cross Site Scripting (XSS) vulnerability. A subscriber-level user can inject malicious scripts through input fields that are not properly sanitized, leading to script execution in the context of other users' browsers [1].
Exploitation
An attacker needs a subscriber-level account on a WordPress site running the vulnerable plugin. The attacker crafts a malicious script and submits it via a vulnerable input field (e.g., shipment tracking number). The script is stored on the server and later executed when a privileged user (such as an admin) views the shipment details, or when visitors view the page. User interaction from the victim is required, such as viewing the infected page [1].
Impact
Successful exploitation allows the attacker to execute arbitrary JavaScript in the browsers of site visitors or administrators. This can be used to steal session cookies, redirect users to malicious sites, inject ads, or deface the website. The stored nature of the XSS amplifies the reach, affecting all visitors [1].
Mitigation
Update the plugin to version 1.5.3.3 or later, which fixes the vulnerability. If unable to update, Patchstack provides a mitigation rule to block attacks. Users can enable auto-updates for vulnerable plugins via Patchstack [1].
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=1.5.3.2
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.