CVE-2026-3474: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in roxnor EmailKit – Email Customizer for WooCommerce & WP
The EmailKit – Email Customizer for WooCommerce & WP plugin for WordPress is vulnerable to arbitrary file read via path traversal in all versions up to, and including, 1.6.3. This is due to the action() function in the TemplateData class passing user-supplied input from the 'emailkit-editor-template' REST API parameter directly to file_get_contents() without any path validation, sanitization, or restriction to an allowed directory. This makes it possible for authenticated attackers, with Administrator-level access, to read arbitrary files on the server (such as /etc/passwd or wp-config.php) by supplying a traversal path. The file contents are stored as post meta and can subsequently be retrieved via the fetch-data REST API endpoint. Notably, the CheckForm class in the same plugin implements proper path validation using realpath() and directory restriction, demonstrating that the developer was aware of the risk but failed to apply the same protections to the TemplateData endpoint.
AI Analysis
Technical Summary
CVE-2026-3474 is a CWE-22 path traversal vulnerability affecting the EmailKit – Email Customizer for WooCommerce & WP plugin for WordPress, present in all versions up to and including 1.6.3. The root cause is the TemplateData class's action() function, which accepts user input from the 'emailkit-editor-template' parameter in the REST API and directly passes it to PHP's file_get_contents() function without any validation or restriction. This lack of path sanitization allows an authenticated attacker with administrator privileges to craft traversal sequences (e.g., ../../) to read arbitrary files on the server filesystem. The retrieved file contents are stored as post meta data and can be accessed later through the fetch-data REST API endpoint, facilitating exfiltration of sensitive information such as configuration files or system files. Interestingly, the plugin’s CheckForm class demonstrates awareness of path traversal risks by implementing realpath() checks and directory restrictions, but these safeguards were not applied to the TemplateData endpoint, indicating inconsistent security practices. The vulnerability requires administrator-level authentication but no additional user interaction, and it can be exploited remotely via the REST API. The CVSS 3.1 score of 4.9 reflects medium severity due to the need for high privileges and the read-only nature of the impact (confidentiality loss without integrity or availability impact). No public exploits have been reported yet, but the vulnerability poses a significant risk to WordPress sites using this plugin, especially those hosting sensitive data or operating in regulated environments.
Potential Impact
The primary impact of CVE-2026-3474 is unauthorized disclosure of sensitive server files, which can lead to information leakage of critical data such as database credentials (wp-config.php), system user information (/etc/passwd), or other confidential files stored on the server. This can facilitate further attacks like privilege escalation, lateral movement, or targeted exploitation by revealing system configurations and secrets. Since the vulnerability requires administrator-level access, it primarily threatens compromised or insider accounts but significantly lowers the barrier for attackers who have gained admin credentials through phishing or other means. The ability to read arbitrary files without integrity or availability impact limits the scope to confidentiality breaches; however, the stolen information can be leveraged for more damaging attacks. Organizations using WooCommerce and WordPress with this plugin are at risk, especially e-commerce sites handling customer data and payment information. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation. The vulnerability also highlights inconsistent security practices in plugin development, which may affect trust and compliance with security standards.
Mitigation Recommendations
To mitigate CVE-2026-3474, organizations should immediately update the EmailKit – Email Customizer for WooCommerce & WP plugin to a patched version once available. Until a patch is released, restrict administrator access to trusted personnel only and monitor admin account activity closely. Implement Web Application Firewall (WAF) rules to detect and block REST API requests containing suspicious path traversal patterns targeting the 'emailkit-editor-template' parameter. Conduct thorough code reviews and penetration testing on custom or third-party plugins to identify similar path traversal flaws. Enforce the principle of least privilege by limiting administrator accounts and using multi-factor authentication to reduce the risk of credential compromise. Additionally, consider disabling or restricting REST API access for authenticated users if not required for business functions. For developers, apply consistent input validation and sanitization using realpath() and directory whitelisting for all file access operations, following the example of the CheckForm class. Regularly audit plugin security and maintain an inventory of installed plugins to quickly respond to vulnerabilities.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Japan, Netherlands
CVE-2026-3474: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in roxnor EmailKit – Email Customizer for WooCommerce & WP
Description
The EmailKit – Email Customizer for WooCommerce & WP plugin for WordPress is vulnerable to arbitrary file read via path traversal in all versions up to, and including, 1.6.3. This is due to the action() function in the TemplateData class passing user-supplied input from the 'emailkit-editor-template' REST API parameter directly to file_get_contents() without any path validation, sanitization, or restriction to an allowed directory. This makes it possible for authenticated attackers, with Administrator-level access, to read arbitrary files on the server (such as /etc/passwd or wp-config.php) by supplying a traversal path. The file contents are stored as post meta and can subsequently be retrieved via the fetch-data REST API endpoint. Notably, the CheckForm class in the same plugin implements proper path validation using realpath() and directory restriction, demonstrating that the developer was aware of the risk but failed to apply the same protections to the TemplateData endpoint.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-3474 is a CWE-22 path traversal vulnerability affecting the EmailKit – Email Customizer for WooCommerce & WP plugin for WordPress, present in all versions up to and including 1.6.3. The root cause is the TemplateData class's action() function, which accepts user input from the 'emailkit-editor-template' parameter in the REST API and directly passes it to PHP's file_get_contents() function without any validation or restriction. This lack of path sanitization allows an authenticated attacker with administrator privileges to craft traversal sequences (e.g., ../../) to read arbitrary files on the server filesystem. The retrieved file contents are stored as post meta data and can be accessed later through the fetch-data REST API endpoint, facilitating exfiltration of sensitive information such as configuration files or system files. Interestingly, the plugin’s CheckForm class demonstrates awareness of path traversal risks by implementing realpath() checks and directory restrictions, but these safeguards were not applied to the TemplateData endpoint, indicating inconsistent security practices. The vulnerability requires administrator-level authentication but no additional user interaction, and it can be exploited remotely via the REST API. The CVSS 3.1 score of 4.9 reflects medium severity due to the need for high privileges and the read-only nature of the impact (confidentiality loss without integrity or availability impact). No public exploits have been reported yet, but the vulnerability poses a significant risk to WordPress sites using this plugin, especially those hosting sensitive data or operating in regulated environments.
Potential Impact
The primary impact of CVE-2026-3474 is unauthorized disclosure of sensitive server files, which can lead to information leakage of critical data such as database credentials (wp-config.php), system user information (/etc/passwd), or other confidential files stored on the server. This can facilitate further attacks like privilege escalation, lateral movement, or targeted exploitation by revealing system configurations and secrets. Since the vulnerability requires administrator-level access, it primarily threatens compromised or insider accounts but significantly lowers the barrier for attackers who have gained admin credentials through phishing or other means. The ability to read arbitrary files without integrity or availability impact limits the scope to confidentiality breaches; however, the stolen information can be leveraged for more damaging attacks. Organizations using WooCommerce and WordPress with this plugin are at risk, especially e-commerce sites handling customer data and payment information. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation. The vulnerability also highlights inconsistent security practices in plugin development, which may affect trust and compliance with security standards.
Mitigation Recommendations
To mitigate CVE-2026-3474, organizations should immediately update the EmailKit – Email Customizer for WooCommerce & WP plugin to a patched version once available. Until a patch is released, restrict administrator access to trusted personnel only and monitor admin account activity closely. Implement Web Application Firewall (WAF) rules to detect and block REST API requests containing suspicious path traversal patterns targeting the 'emailkit-editor-template' parameter. Conduct thorough code reviews and penetration testing on custom or third-party plugins to identify similar path traversal flaws. Enforce the principle of least privilege by limiting administrator accounts and using multi-factor authentication to reduce the risk of credential compromise. Additionally, consider disabling or restricting REST API access for authenticated users if not required for business functions. For developers, apply consistent input validation and sanitization using realpath() and directory whitelisting for all file access operations, following the example of the CheckForm class. Regularly audit plugin security and maintain an inventory of installed plugins to quickly respond to vulnerabilities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-03T13:02:05.586Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bdda56b462d409683a8c08
Added to database: 3/20/2026, 11:37:58 PM
Last enriched: 3/20/2026, 11:40:06 PM
Last updated: 3/21/2026, 3:53:36 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.