CVE-2026-131609 in Germanized for WooCommerce Plugininfo

Summary

by MITRE • 11/21/2026

The Germanized for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'billing_address.first_name (Store API checkout) → stored on parent order; withdrawal get_first_name() fallback' parameter in all versions up to, and including, 4.1.8 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. The payload is planted via an unauthenticated guest checkout order's billing first name through the WooCommerce Store API, with execution triggered by a subsequent unauthenticated withdrawal request submission whose nonce is publicly available on the /withdraw-from-contract/ page.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The Germanized for WooCommerce plugin, widely utilized in WordPress environments to facilitate region-specific e-commerce operations, contains a critical security flaw identified as Stored Cross-Site Scripting within versions up to and including 4.1.8. This vulnerability stems from insufficient input sanitization and output escaping mechanisms embedded deep within the plugin's data handling logic. Specifically, the defect resides in how the billing address first name field is processed during checkout operations via the WooCommerce Store API. When an unauthenticated user completes a guest checkout order, the provided first name value is stored directly into the parent order record without adequate validation or encoding checks. This lack of rigorous filtering allows malicious actors to inject arbitrary JavaScript code that persists within the database alongside legitimate customer data.

The operational impact of this vulnerability extends beyond simple data storage because the injected payload remains active and executable under specific conditions tied to the plugin's withdrawal functionality. The attack vector is triggered when an unauthenticated user submits a request for withdrawing funds from a contract, which relies on a nonce value that is publicly accessible on the /withdraw-from-contract/ page. Because the nonce required for this action is not sufficiently protected or randomized in a way that prevents prediction or reuse by external parties, attackers can craft requests that exploit the stored script. When these withdrawal requests are processed, the system retrieves the tainted first name data and renders it into the response without proper escaping, causing the browser to execute the embedded malicious scripts. This execution occurs within the context of the victim's session if they interact with affected pages or when the payload is rendered in administrative interfaces that display order details.

From a technical classification perspective, this vulnerability aligns closely with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The stored nature of the attack means it qualifies under persistent XSS vectors where the malicious payload is saved on the target server and served to users later. Furthermore, in terms of tactical mapping within the MITRE ATT&CK framework for enterprise security, this behavior corresponds to T1059.007 JavaScript Execution via Web Browsers and potentially T1133 Free Account Initial Access if attackers leverage public-facing endpoints like guest checkout flows to establish initial footholds or disrupt service integrity. The combination of unauthenticated access points and predictable nonces significantly lowers the barrier for exploitation, allowing even low-skilled threat actors to execute code injection attacks against high-traffic e-commerce sites.

Mitigation strategies must address both immediate remediation and long-term architectural improvements. Administrators running affected versions should immediately update the Germanized plugin to version 4.1.9 or later where these sanitization issues have been resolved by developers implementing stricter input validation and robust output encoding practices. In addition to updating, organizations should implement Web Application Firewalls configured with rulesets capable of detecting and blocking XSS payloads in POST requests targeting WooCommerce endpoints. It is also advisable to review server-side configurations to ensure that nonces used for sensitive operations like withdrawals are generated securely using cryptographic random number generators and validated strictly against the current user session context rather than being exposed publicly or reused across different contexts. Regular security audits focusing on API endpoint handling of user-supplied data will further reduce the risk profile associated with such integrations.

Responsible

Wordfence

Reservation

11/17/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00550

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!