---
id: "CVE-2026-109231"
kind: "vulnerability"
aliases: ["CVE-2026-109231"]
title: "Germanized for WooCommerce: activation token reuse exposes buyers' order data"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["germanized", "package", "self-hosted", "woocommerce", "wordpress"]
not_affected_if: ["default-config", "managed-hosting", "registration-disabled"]
published_at: "2026-10-31T10:16:37+00:00"
first_seen_at: "2026-10-31T10:34:56+00:00"
updated_at: "2026-10-31T10:36:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109231", "first_seen_at": "2026-10-31T10:34:56+00:00"}]
---

# Germanized for WooCommerce: activation token reuse exposes buyers' order data

Germanized for WooCommerce up to and including 4.1.4 leaves a customer's activation token valid after the account email changes. An authenticated attacker can reuse it to take over a guest order and read the buyer's name, address, phone number and purchased items.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Germanized for WooCommerce version in the WordPress plugins screen or `wp plugin get woocommerce-germanized --field=version`
- Check whether "Disable login for unactivated customers" is set to No in the Germanized double opt-in settings
- Check whether public customer registration is enabled in WooCommerce account settings

## Timeline

- 2026-10-31T10:34:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109231

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_