HomeWordPress vulnerabilitiesGermanized for WooCommerce
Germanized for WooCommerce vulnerabilities
Germanized for WooCommerce has 3 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 3
- Active installs
- 70,000+
- Latest version
- 4.1.7
- Last updated
- 9 Nov 2026
- Most recent
- 21 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-131609 | High 7.2 | Up to 4.1.8 | No fixed version yet | 1 d ago |
| Broken access control CVE-2026-109231 | Medium 4.3 | Up to 4.1.4 | Fixed in a later version (latest 4.1.7) | 31 Oct 2026 |
| Remote code execution CVE-2026-2582 | Medium 6.5 | Up to 3.20.5 | Fixed in a later version (latest 4.1.7) | 14 Apr 2026 |
Read the published descriptions
- CVE-2026-131609, 21 Nov 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. CVE record
- CVE-2026-109231, 31 Oct 2026
- The Germanized for WooCommerce plugin for WordPress is vulnerable to Unauthorized Access of Private Data via Activation Token Reuse in versions up to, and including, 4.1.4. This is due to the `on_user_email_changed` hook - which is responsible for rotating the activation token and recording a pending-email-change marker on an unactivated Customer account - only being registered inside the `is_double_opt_in_login_enabled()` branch when "Disable login for unactivated customers" is set to Yes, leaving the original `?activate=` token valid and entirely unbound to the email address it was issued for when that setting is No. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change their account email to a victim's billing email via the standard `/my-account/edit-account/` form and then redeem their original activation token through `customer_account_activate()`, triggering `link_customer_past_orders()` to reassign any matching guest order to the attacker's account and exposing the original buyer's billing name, street address, phone number, and purchased items on the attacker's My Account order page. Exploitation requires the site to have double opt-in enabled with "Disable login for unactivated customers" explicitly set to No (a non-default configuration), public customer registration enabled, and the original activation token redeemed within its one-day expiry window. CVE record
- CVE-2026-2582, 14 Apr 2026
- The The Germanized for WooCommerce plugin for WordPress is vulnerable to arbitrary shortcode execution via 'account_holder' parameter in all versions up to, and including, 3.20.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. CVE record
What to do if you run Germanized for WooCommerce
If you run Germanized for WooCommerce, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Germanized for WooCommerce vulnerabilities
Free. We email you when a new vulnerability is published for Germanized for WooCommerce, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.