dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-39540

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Subscriber Cross Site Scripting (XSS) in Shipment Tracker for Woocommerce <= 1.5.3.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored Cross Site Scripting (XSS) vulnerability exists in the Shipment Tracker for WooCommerce plugin (versions <= 1.5.3.2). The flaw allows authenticated subscribers to inject malicious JavaScript code through shipment tracking input fields. Since this is a stored XSS, the malicious payload executes whenever users view the affected content, potentially leading to session hijacking, cookie theft, or credential harvesting.

MitigationUpgrade to the latest version of Shipment Tracker for WooCommerce (or at minimum to version 1.5.3.3 if available) to obtain the security patch. If no patch exists, implement output encoding on all user-supplied data displayed in tracking-related pages and apply input validation/sanitization on the server side.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Shipment Tracker for WooCommerce is installed
    Navigate to WordPress admin > Plugins and look for 'Shipment Tracker for WooCommerce' in the installed plugins list
    Affected if The plugin does not appear in the installed plugins list, then you are not affected
  2. Check the installed plugin version
    In WordPress admin > Plugins, find Shipment Tracker for WooCommerce and view the version number displayed beneath the plugin name
    Affected if The displayed version is 1.5.3.2 or lower, indicating the vulnerable version is installed
  3. Confirm subscriber-level user access exists
    Go to WordPress admin > Users > Roles or use a user management plugin to verify if any user accounts have the 'Subscriber' role assigned
    Affected if There are no subscriber accounts configured, the attack surface is significantly reduced but the plugin may still contain the vulnerability
  4. Inspect shipment tracking input functionality
    As a subscriber user, attempt to access any front-end forms or admin interfaces where shipment tracking numbers or carrier information can be entered (typically found on order history or tracking pages)
    Affected if The tracking input fields are present and accept user-supplied data without visible sanitization indicators, the XSS vulnerability could be triggered

You are affected if the Shipment Tracker for WooCommerce plugin is installed with version 1.5.3.2 or lower and subscriber users can access shipment tracking input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Shipment Tracker for WooCommerce (or at minimum to version 1.5.3.3 if available) to obtain the security patch. If no patch exists, implement output encoding on all user-supplied data displayed in tracking-related pages and apply input validation/sanitization on the server side.

Recommended fix Moderate confidence

1.5.3.3 (or latest available version)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Shipment Tracker for Woocommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 1.5.3.3 or higher
  6. 6. Test shipment tracking functionality to ensure the update did not break existing features
  7. 7. Clear any caching plugins or server-side caches if applicable

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39540 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39540 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data