VulnerabilityPublished 31 Oct 2026

CVE-2026-109231: Germanized for WooCommerce (WordPress plugin) · Improper Enforcement of Behavioral Workflow

Affects Germanized for WooCommerce (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 31 Oct 2026, 09:51 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Wordfence)	CVSS 3.1	4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
vendideroGermanized for WooCommerce	Affected <=4.1.4	Fixed in–

AI-suggested

Since the vulnerability depends on a non-default configuration ('Disable login for unactivated customers' set to No), administrators should consider setting this option to Yes to ensure the activation token rotation hook is properly registered. Alternatively, disabling public customer registration or ensuring tokens cannot be reused may mitigate the risk. Monitor vendor advisories for an official fix and apply updates when available.

Description

The Germanized for WooCommerce WordPress plugin up to version 4.1.4 has a vulnerability allowing unauthorized access to private customer data via activation token reuse. This occurs when the 'Disable login for unactivated customers' setting is set to No (non-default) and double opt-in is enabled. An authenticated attacker with Subscriber-level access can change their account email to a victim's billing email and redeem their original activation token, causing guest orders to be linked to the attacker's account and exposing sensitive billing information. Exploitation requires public customer registration and token redemption within one day.

Impact

The vulnerability allows authenticated attackers with Subscriber-level access to access private customer data, including billing name, street address, phone number, and purchased items, by reusing activation tokens and linking guest orders to their account. This leads to unauthorized disclosure of sensitive personal and purchase information. The impact is limited to sites with double opt-in enabled, public customer registration, and the 'Disable login for unactivated customers' setting set to No. The CVSS score is 4.3 (medium severity), indicating limited impact on confidentiality and no impact on availability or system integrity.

Summary

CVE-2026-109231 describes an improper enforcement of behavioral workflow (CWE-841) in the Germanized for WooCommerce plugin for WordPress. The vulnerability arises because the activation token rotation hook is only registered when the 'Disable login for unactivated customers' setting is Yes. When set to No, the original activation token remains valid and unbound to the email it was issued for. An attacker with Subscriber-level privileges can change their email to a victim's billing email and redeem the original activation token, triggering reassignment of guest orders to their account and exposing the victim's billing name, address, phone number, and purchased items. The vulnerability affects versions up to and including 4.1.4 and requires specific configuration settings and timely token redemption.

CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence or timeframe.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2026, 09:39 UTC

WeaknessesCWE-841

Technical details

References

Community reviews

Related threats