Read the docs

Activation token reuse in Germanized for WooCommerce exposes orders

Priority LOW 20CWE-841Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

Germanized for WooCommerce is affected in versions up to and including 4.1.4. The activation token of an unactivated account stays valid after an email change (CWE-841). An attacker with Subscriber-level access can change their email to a victim's billing email, redeem their original token, and view the victim's billing name, street address, phone number and purchased items. Exploitation requires double opt-in enabled, "Disable login for unactivated customers" set to No, and public customer registration enabled.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00369 31st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
vendideroGermanized for WooCommerceup to 4.1.4—No fix listedCNA
  • Germanized for WooCommerce Vendorvendidero Affected up to 4.1.4 Fixed in — No fix listed CNA

Remediation

No fixed version is listed for Germanized for WooCommerce.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Timeline

  1. 2026-10-31 Threatist record created from CVE-2026-109231
  2. 2026-10-31 Alias added: GHSA-c79g-76jm-qrx5
  3. 2026-11-03 CISA SSVC decision points changed

References

  • TI-2026-02205 Germanized for WooCommerce <= 3.20.5 - Unauthenticated Arbitrary Shortcode Execution CVSS 3.1MEDIUM 6.5
  • TI-2026-63878 WordPress Trusted Shops Easy Integration for WooCommerce plugin <= 2.0.6 - Cross Site Scripting (XSS) vulnerability CVSS 3.1HIGH 7.1
  • TI-2026-46671 WordPress Shiptastic for WooCommerce plugin <= 5.1.0 - Insecure Direct Object References (IDOR) vulnerability CVSS 3.1MEDIUM 5.3

Sources