CVE-2026-130322 in EU Order Withdrawal Button Plugininfo

Summary

by MITRE • 11/20/2026

The EU Order Withdrawal Button for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HTTP_USER_AGENT' parameter in all versions up to, and including, 2.4.6 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. Execution requires an Administrator or Shop Manager to open the Withdrawals Preview modal and click the injected note element, which the attacker can enlarge via a retained style attribute to cover the entire note area. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The EU Order Withdrawal Button for WooCommerce plugin is susceptible to a Stored Cross-Site Scripting vulnerability affecting all versions up to and including 2.4.6. This security flaw stems from insufficient input sanitization and output escaping mechanisms within the application code, specifically concerning the handling of the HTTP_USER_AGENT parameter. The vulnerability allows unauthenticated attackers to inject arbitrary web scripts into pages that are subsequently rendered by the WordPress environment. Unlike reflected XSS attacks where exploitation is immediate upon request, this stored variant persists in the system's data storage, meaning the malicious payload remains active until it is explicitly triggered or removed from the database.

The technical mechanism of the exploit relies on the attacker manipulating the HTTP_USER_AGENT header during interaction with the plugin. Because the application fails to properly sanitize this input before storing it and subsequently escapes it inadequately when rendering output, the injected script becomes part of the page content. The operational impact is significant because the execution context involves privileged users. Specifically, successful exploitation requires an Administrator or Shop Manager to open the Withdrawals Preview modal within the WordPress dashboard. Once inside this interface, the user must click on a specific note element that has been compromised by the attacker's injection.

To facilitate social engineering and ensure the victim interacts with the malicious payload, attackers can utilize CSS styling attributes retained during the input phase to enlarge the injected note element so it covers the entire visible area of the modal. This visual manipulation increases the likelihood that an administrator will inadvertently click on the malicious link or script trigger while attempting to perform legitimate administrative tasks. The requirement for a privileged user action means that this is not an automated remote code execution vector, but rather a targeted attack requiring human interaction with the compromised interface elements.

From a classification perspective, this vulnerability aligns with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The specific nature of storing malicious scripts in server-side storage for later retrieval corresponds to Stored XSS patterns often associated with ATT&CK technique T1059, specifically the sub-technique for JavaScript execution within web browsers. This classification highlights the risk of persistent threats that linger in application data stores and require administrative intervention to manifest their impact.

Mitigation strategies should prioritize immediate patching by upgrading the EU Order Withdrawal Button plugin to a version newer than 2.4.6, where these sanitization and escaping issues have been addressed by the developers. In scenarios where an upgrade is not immediately feasible, administrators can implement web application firewall rules to filter out malicious payloads in HTTP headers before they reach the application logic. Additionally, enforcing strict Content Security Policy directives can help mitigate the impact of any successfully injected scripts by restricting the sources from which executable content can be loaded. Regular security audits and code reviews focusing on input validation for all user-controllable data points are essential preventive measures against such vulnerabilities.

Responsible

Wordfence

Reservation

11/16/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00829

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!