Security readout for executives and security teams
Plain-English summary
CVE-2026-3474 affects the EmailKit WordPress plugin for WooCommerce sites. An authenticated WordPress administrator could use a vulnerable REST API parameter to read arbitrary server files. This is not a remote unauthenticated takeover, but it can expose sensitive configuration files, including WordPress secrets, if an admin account is compromised or malicious.
Executive priority
Treat as a targeted confidentiality risk. Prioritize WooCommerce sites with many administrators, third-party site managers, or prior admin-account concerns. It is lower urgency than unauthenticated remote code execution, but sensitive file exposure can lead to credential theft and broader compromise.
Technical view
EmailKit versions up to and including 1.6.3 pass the user-controlled emailkit-editor-template REST API parameter to file_get_contents() without path validation. The issue is CWE-22 path traversal. CVSS is 4.9: network reachable, low complexity, administrator privileges required, no user interaction, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is limited to WordPress sites running EmailKit up to 1.6.3, especially WooCommerce environments. Exploitation requires Administrator-level authentication, so the main risk is compromised admin accounts, insider misuse, or excessive administrator access granted to third parties.
Exploitation context
The CVE record and Wordfence describe arbitrary file read through a REST API workflow, with retrieved contents stored as post meta and accessible later. CISA KEV is not indicated in the provided data, and no provided source states active exploitation.
Researcher notes
The source bundle points to TemplateData.php lines around the unsafe file_get_contents() usage and a WordPress Trac changeset. Evidence indicates the developer used safer realpath-based validation elsewhere, but the provided data does not clearly name a fixed version. Validate remediation against official plugin or Wordfence guidance.
Mitigation direction
- Identify WordPress sites running the EmailKit plugin.
- Check whether installed EmailKit versions are 1.6.3 or earlier.
- Review Wordfence, WordPress plugin, and vendor guidance for the fixed release.
- Update EmailKit when a fixed version is available from trusted sources.
- Disable or remove EmailKit where it is not business-critical.
- Limit WordPress administrator accounts to trusted users only.
Validation and detection
- Inventory EmailKit installations across WordPress and WooCommerce sites.
- Confirm installed plugin versions against the vulnerable range.
- Review administrator account lists for unnecessary or suspicious users.
- Review logs for REST requests involving emailkit-editor-template or fetch-data endpoints.
- Inspect post metadata for unexpected stored file contents if compromise is suspected.
- Do not validate by attempting to read sensitive system files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3474 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d8c11ebc-5c83-46a2-a8dd-b838cd50ddc6?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/emailkit/trunk/includes/Admin/Api/TemplateData.php#L49CVE reference
- https://plugins.trac.wordpress.org/browser/emailkit/tags/1.6.2/includes/Admin/Api/TemplateData.php#L49CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3484455%40emailkit&new=3484455%40emailkit&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
