Skip to main content

Germanized For Woocommerce CVE-2026-2582

| EUVDEUVD-2026-22223 MEDIUM
Code Injection (CWE-94)
2026-04-14 Wordfence
6.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WooCommerce site using scanner
  2. Delivery
    Locate direct-debit payment form
  3. Exploit
    Inject shortcode in account_holder field
  4. Execution
    Bypass validation check
  5. Persist
    Shortcode processor executes payload
  6. Impact
    Impact depends on available shortcodes

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) indicates a network-accessible, low-complexity attack requiring no privileges or user interaction, resulting in confidentiality and integrity impact without availability loss. The 6.5 base score reflects moderate-to-high real-world risk for affected sites. However, actual exploitation impact depends on which shortcodes are registered in the WordPress environment-if only benign shortcodes exist, the practical impact may be limited; if dangerous ones are present (e.g., admin-only shortcodes from premium plugins), attackers can escalate to full RCE. The unauthenticated attack vector significantly raises risk for publicly accessible WordPress installations. No EPSS, KEV status, or POC availability data provided, but the combination of trivial access vector and trivial complexity suggests this is a genuine priority for vulnerability management, not a CVSS-inflation case.

Exploit ScenarioDerived

An attacker crafts a malicious POST request to the WooCommerce direct-debit payment processing endpoint with the 'account_holder' parameter containing a shortcode payload such as [malicious_shortcode] or a chain of shortcodes targeting known plugins. The request bypasses authentication (PR:N) and reaches the vulnerable code path, where do_shortcode() processes the unsanitized input and executes the embedded shortcode. Depending on available shortcodes in the environment, this could leak sensitive information, modify site content, or escalate to remote code execution if a plugin provides a shortcode with PHP execution capabilities.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 14, 2026

Unauthenticated attackers can execute arbitrary WordPress shortcodes in the Germanized for WooCommerce plugin (all versions up to 3.20.5) via the 'account_holder' parameter, which bypasses shortcode validation in the do_shortcode() function. This enables remote code execution with medium severity (CVSS 6.5) affecting any WordPress site with the vulnerable plugin installed. No public exploit code or active exploitation has been confirmed at the time of analysis.

RemediationAI

Update the Germanized for WooCommerce plugin to version 3.20.6 or later, which implements proper input validation and sanitization on the 'account_holder' parameter before shortcode execution. Site administrators should navigate to WordPress Dashboard → Plugins → Installed Plugins, locate Germanized for WooCommerce, and apply the update immediately. If a patched version is not yet available in the update feed, temporarily disable the direct-debit payment gateway in WooCommerce settings to prevent exploitation. Consult the Wordfence advisory at the provided URL for additional security context and confirmation of patch availability.

Affected VersionsENISA

Germanized for WooCommerce 0 ≤3.20.5

Affected Packages

euvd germanized_for_woocommerce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from CWE-94 (Improper Control of Generation of Code via Code Injection) in the direct-debit gateway payment processing code. The plugin accepts the 'account_holder' parameter and passes it directly to WordPress's do_shortcode() function without validating or sanitizing the input first. WordPress shortcodes provide a powerful templating mechanism-any registered shortcode can be invoked by an attacker, potentially including shortcodes provided by other plugins or themes that may execute PHP code or access sensitive data. The flaw exists in the gateway handler class at the referenced plugin path, where the parameter flows from user input to the shortcode processor without intermediate validation controls.

Know when Germanized For Woocommerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 75% exploitable
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy