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

CVE-2026-6417

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

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
The GLS Shipping for WooCommerce plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'failed_orders' parameter in all versions up to, and including, 1.4.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 · high confidence

The GLS Shipping for WooCommerce plugin for WordPress is vulnerable to reflected cross-site scripting (XSS) via the 'failed_orders' parameter in versions up to 1.4.0. The vulnerability stems from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript through malicious URLs that trick users into clicking links.

MitigationUpdate the plugin to a version newer than 1.4.0 that includes proper input sanitization and output escaping for the 'failed_orders' parameter, or implement immediate input validation and escaping if a patched version is unavailable.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 GLS Shipping for WooCommerce is installed
    In WordPress admin, go to Plugins > Instored Plugins and look for 'GLS Shipping for WooCommerce', or check the plugin files in /wp-content/plugins/ for the GLS plugin directory
    Affected if The plugin is present in the installation
  2. Check installed plugin version
    View the plugin details in WordPress admin (click 'View Details' on the plugin) or open the main plugin PHP file and look for the Version header comment
    Affected if Version is 1.4.0 or lower
  3. Confirm failed_orders parameter is accessible
    Check if the WordPress site has any pages or endpoints that accept a 'failed_orders' GET or POST parameter; this typically appears in admin pages or frontend order tracking views
    Affected if The parameter is accepted and processed by the plugin
  4. Inspect parameter handling in source code
    Examine the main plugin PHP files for code handling the 'failed_orders' parameter; look for lack of sanitization functions like sanitize_text_field() and escaping functions like esc_html() or esc_attr() before output
    Affected if The parameter value is output without proper sanitization and escaping

You are affected if the GLS Shipping for WooCommerce plugin version is 1.4.0 or lower AND the failed_orders parameter is processed by your site without sanitization and escaping.

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

Update the plugin to a version newer than 1.4.0 that includes proper input sanitization and output escaping for the 'failed_orders' parameter, or implement immediate input validation and escaping if a patched version is unavailable.

Recommended fix Moderate confidence

1.4.1 or later (update to the latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'GLS Shipping for WooCommerce' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. Verify the update completed successfully by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6417 — 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-6417 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