Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/obtain subscriber account
-
DeliveryCall send_test_mail() with PHP payload
-
ExploitWrite webshell to uploads directory
-
ExecutionRequest file to execute PHP as web server
-
ImpactFull site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Exploitation Conditions | Exploitation requires an authenticated account with subscriber-level privileges or higher (CVSS PR:L), so the realistic exposure is highest on stores that allow open customer/subscriber self-registration - common for WooCommerce but not universal. The specific vulnerable code path is the plugin's send_test_mail() function, which lacks sufficient authorization checks and input sanitization and writes user-controlled PHP into executable files in the WordPress uploads directory; the server must therefore allow PHP execution from that uploads path (not hardened/blocked) for code execution to succeed. The plugin affected is specifically the Email Customizer for WooCommerce (Pro) by ThemeHigh at versions up to and including 3.9.5. The primary limiting factors are the need for a valid low-privilege account and any server-side restriction on executing PHP from uploads. |
| Impact | This is a genuine high-priority vulnerability, not an inflated-CVSS artifact. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes network-reachable, low-complexity exploitation requiring only PR:L - and the description independently confirms this maps to subscriber-level accounts, the lowest meaningful authenticated tier on most WordPress/WooCommerce sites that allow customer registration. The signals are internally consistent: CVSS network/low-complexity aligns with the described send_test_mail() flaw writing user-controlled PHP to executable files in the uploads directory, yielding full RCE. The limiting factor is the authentication requirement (PR:L): an attacker needs a valid low-privilege account, so sites that permit open customer/subscriber registration (common for WooCommerce stores) are far more exposed than those that do not. Key data is MISSING and must be flagged: no EPSS score, no CISA KEV listing, and no POC/exploit availability were provided, so exploitation status is 'no public exploit identified at time of analysis' and real-world exploitation probability cannot be quantified from the input. The absence of KEV/EPSS does not lower the intrinsic severity - RCE on authenticated low-privilege access against an internet-facing e-commerce platform warrants prompt patching regardless of current exploitation telemetry. |
| Exploit ScenarioDerived | An attacker registers or obtains a subscriber-level account on a WooCommerce store running the vulnerable plugin, then sends a crafted request to the send_test_mail() function containing malicious PHP, which is written to an executable file in the wp-content uploads directory. The attacker then requests that file over HTTP to execute arbitrary PHP and achieve full site compromise. No public POC or exploit code was identified in the provided intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Remote code execution in ThemeHigh's Email Customizer for WooCommerce (Pro) through version 3.9.5 allows any authenticated user with subscriber-level access or higher to write attacker-controlled PHP into executable files inside the WordPress uploads directory through the plugin's send_test_mail() function, leading to full site compromise. The assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8) makes clear that the low-privilege account requirement is the main gate; exposure is greatest on WooCommerce stores that permit open customer/subscriber self-registration rather than manual account approval. Code execution also depends on the server permitting PHP to run from the uploads path, so sites that already harden that directory are materially less exposed, and no public exploit code has been identified at time of analysis.
RemediationAI
Upgrade Email Customizer for WooCommerce (Pro) to a release newer than 3.9.5; the vendor changelog at https://www.themehigh.com/changelog/?view=22 is the authoritative place to confirm the exact patched version, since the provided data does not state a specific fixed version number, and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/e8d4cd3d-68ad-45ec-b4b3-e705da4e6628?source=cve should be checked for the same detail. Until the update is applied, the highest-value compensating control is to prevent PHP execution in the uploads directory: on Apache use RemoveHandler/php_flag engine off rules or an .htaccess directive scoped to wp-content/uploads, and on nginx add a location matching wp-content/uploads with a deny rule for \.php requests (return 403); the trade-off is that legitimate media files continue to work but any plugin or theme that relies on executing PHP it dropped into uploads would break, which is rare and usually undesirable anyway. Also reduce the attack surface by disabling open subscriber/customer self-registration or manually approving new accounts, since the flaw requires only subscriber-level access; the trade-off is friction or lost sign-ups for stores that depend on open registration. As a secondary measure, restrict or block access to the plugin's test-mail functionality (for example, deny requests reaching send_test_mail through admin-ajax or admin-post endpoints at the WAF or reverse proxy for non-administrator sessions), and audit wp-content/uploads for recently created .php files and remove them, treating any found as indicators of compromise requiring credential rotation and a full malware review.
Affected VersionsENISA
Affected Packages
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 root cause class is CWE-74, injection through improper neutralization of special elements, compounded here by missing authorization checks. In the affected plugin, the send_test_mail() routine is intended to let an administrator trigger a preview/test email, but it neither verifies that the caller holds an administrative capability nor sanitizes the user-supplied content before persisting it. The result is that user-controlled PHP is written out as a file into the WordPress uploads directory (wp-content/uploads and its subdirectories), which is normally writable by the web server. If that path is served by the web tier with PHP processing enabled, requesting the dropped file executes the injected code in the context of the web server user, giving the attacker arbitrary code execution and, from there, full control of the WordPress installation. The CPE cpe:2.3:a:themehigh:email_customizer_for_woocommerce_(pro):*:*:*:*:*:*:*:* identifies the commercial Pro offering of the WooCommerce email customization plugin as the affected product line, distinguishing it from any free or differently named ThemeHigh variants. Because the vector is network-reachable with PR:L and no user interaction, and scope is unchanged with high confidentiality, integrity and availability impact, the practical severity rests on how easily an attacker can obtain a subscriber-level account on the target store and whether PHP execution from uploads is blocked.
Know when PHP 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
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Remote, low-complexity, no user interaction; PR:L because a subscriber-level authenticated account is required; full RCE gives complete C/I/A impact within the unchanged WordPress scope.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Email Customizer for WooCommerce (Pro) plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 3.9.5. This is due to insufficient authorization and input sanitization in the send_test_mail() function, which allows user-controlled PHP code to be written to executable files in the uploads directory. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute arbitrary PHP code on the server, leading to full site compromise.
Executive ViewAI
ThemeHigh's Email Customizer for WooCommerce (Pro) through version 3.9.5 can be abused by an authenticated subscriber-level user to achieve full site compromise on WooCommerce stores that allow open customer/subscriber registration. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so affected organizations must rely on compensating controls until a fix is available. Leadership should care because successful exploitation could lead to data theft, site defacement, malware distribution, and loss of customer trust.
No vendor-released patch identified at time of analysis. Interim mitigations: disable Email Customizer for WooCommerce (Pro) plugin on exposed sites; require manual approval for new customer/subscriber accounts or disable open registration; prevent PHP execution in wp-content/uploads; deploy WAF rules targeting send_test_mail(); monitor uploads and plugin logs for suspicious PHP files; apply vendor patch once released.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-101864
GHSA-4pxj-xxwx-q7rf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB