CVE-2026-3474

{"id": "CVE-2026-3474", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security@wordfence.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 1.2}]}, "published": "2026-03-21T00:16:28.207", "references": [{"url": "https://plugins.trac.wordpress.org/browser/emailkit/tags/1.6.2/includes/Admin/Api/TemplateData.php#L48", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/emailkit/tags/1.6.2/includes/Admin/Api/TemplateData.php#L49", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/emailkit/tags/1.6.2/includes/Admin/Api/TemplateData.php#L50", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/emailkit/trunk/includes/Admin/Api/TemplateData.php#L48", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/emailkit/trunk/includes/Admin/Api/TemplateData.php#L49", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/emailkit/trunk/includes/Admin/Api/TemplateData.php#L50", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3484455%40emailkit&new=3484455%40emailkit&sfp_email=&sfph_mail=", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/d8c11ebc-5c83-46a2-a8dd-b838cd50ddc6?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-22"}]}], "descriptions": [{"lang": "en", "value": "The EmailKit \u2013 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."}, {"lang": "es", "value": "El plugin EmailKit \u2013 Email Customizer for WooCommerce & WP para WordPress es vulnerable a la lectura arbitraria de archivos a trav\u00e9s de salto de ruta en todas las versiones hasta la 1.6.3, inclusive. Esto se debe a que la funci\u00f3n action() en la clase TemplateData pasa la entrada proporcionada por el usuario del par\u00e1metro de la API REST 'emailkit-editor-template' directamente a file_get_contents() sin ninguna validaci\u00f3n de ruta, saneamiento o restricci\u00f3n a un directorio permitido. Esto hace posible que atacantes autenticados, con acceso de nivel de Administrador, lean archivos arbitrarios en el servidor (como /etc /passwd o wp-config.php) al proporcionar una ruta de salto. El contenido del archivo se almacena como metadatos de publicaci\u00f3n y posteriormente puede recuperarse a trav\u00e9s del endpoint de la API REST fetch-data. Cabe destacar que la clase CheckForm en el mismo plugin implementa una validaci\u00f3n de ruta adecuada utilizando realpath() y restricci\u00f3n de directorio, lo que demuestra que el desarrollador era consciente del riesgo pero no aplic\u00f3 las mismas protecciones al endpoint TemplateData."}], "lastModified": "2026-04-22T21:32:08.360", "sourceIdentifier": "security@wordfence.com"}