CVE-2026-6417: XSS in GLS Shipping for WooCommerce
Platform
wordpress
Component
gls-shipping-for-woocommerce
Fixed in
1.4.1
CVE-2026-6417 describes a Reflected Cross-Site Scripting (XSS) vulnerability discovered in the GLS Shipping for WooCommerce plugin for WordPress. This vulnerability allows unauthenticated attackers to inject arbitrary web scripts, potentially leading to session hijacking or data theft. The vulnerability affects versions 0.0.0 through 1.4.0, and a patch is available in version 1.4.1.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Impact and Attack Scenarios
Successful exploitation of CVE-2026-6417 allows an attacker to execute malicious JavaScript code within the context of a user's browser session on the WordPress site. This can be achieved by crafting a malicious URL containing the 'failed_orders' parameter and tricking a user into clicking it. The attacker could then steal session cookies, redirect the user to a phishing site, or deface the website. The impact is amplified if the targeted website handles sensitive user data or financial transactions, as the attacker could gain access to this information. The attack vector is reflected, meaning the attacker needs to entice the victim to click a crafted link, but the potential consequences are significant.
Exploitation Context
CVE-2026-6417 was published on 2026-05-14. The vulnerability is considered Medium severity. Currently, there are no publicly known active campaigns exploiting this specific vulnerability. No information is available regarding its presence on KEV or EPSS. Monitor security advisories and threat intelligence feeds for any updates regarding exploitation attempts.
Threat Intelligence
Exploit Status
CISA SSVC
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- None — unauthenticated. No login or credentials needed to exploit.
- User Interaction
- Required — victim must take an action: open a file, click a link, or visit a crafted page.
- Scope
- Changed — successful attack can pivot beyond the vulnerable component to other systems or the host OS.
- Confidentiality
- Low — partial or indirect data access. Attacker gains limited information.
- Integrity
- Low — attacker can modify some data with limited scope or impact.
- Availability
- None — no availability impact. Service remains fully operational.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
Mitigation and Workarounds
The primary mitigation for CVE-2026-6417 is to immediately upgrade the GLS Shipping for WooCommerce plugin to version 1.4.1 or later. If upgrading is not immediately feasible, consider implementing temporary workarounds such as input validation and output encoding on the 'failedorders' parameter. Web Application Firewalls (WAFs) configured to detect and block XSS payloads can also provide a layer of protection. Carefully review any custom code interacting with the 'failedorders' parameter to ensure proper sanitization and escaping.
How to fix
Update to version 1.4.1, or a newer patched version
Frequently asked questions
What is CVE-2026-6417 — XSS in GLS Shipping for WooCommerce?
CVE-2026-6417 is a Reflected Cross-Site Scripting (XSS) vulnerability affecting the GLS Shipping for WooCommerce plugin. It allows attackers to inject malicious scripts via the 'failed_orders' parameter, potentially compromising user sessions and data.
Am I affected by CVE-2026-6417 in GLS Shipping for WooCommerce?
You are affected if you are using GLS Shipping for WooCommerce versions 0.0.0 through 1.4.0. Check your plugin version and upgrade immediately if you are vulnerable.
How do I fix CVE-2026-6417 in GLS Shipping for WooCommerce?
Upgrade the GLS Shipping for WooCommerce plugin to version 1.4.1 or later. This resolves the XSS vulnerability by implementing proper input sanitization and output escaping.
Is CVE-2026-6417 being actively exploited?
As of the current date, there are no publicly known active campaigns exploiting CVE-2026-6417. However, it's crucial to apply the patch promptly to prevent potential future attacks.
Where can I find the official GLS Shipping advisory for CVE-2026-6417?
Refer to the official WooCommerce plugin repository and the GLS Shipping for WooCommerce plugin page for the latest security updates and advisories related to CVE-2026-6417.
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Scan your WordPress project now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...