{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5957 is a medium-severity path traversal vulnerability in roxnor EmailKit – Email Customizer for WooCommerce \u0026 WP, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5957 and fix it if it is affected.\n\nWhat it is: CVE-2026-5957 is a medium-severity path traversal vulnerability in roxnor EmailKit – Email Customizer for WooCommerce \u0026 WP, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5957 in the wild and no public exploit code.\n\nAffected product: roxnor EmailKit – Email Customizer for WooCommerce \u0026 WP. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5957/ (Markdown: https://insights.sbomify.com/CVE-2026-5957/index.md)","id":"CVE-2026-5957","markdown":"https://insights.sbomify.com/CVE-2026-5957/index.md","name":"CVE-2026-5957","record":{"aliases":["GHSA-28j2-6q62-7r48"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers with Author-level access can read arbitrary files, including wp-config.php, via a path traversal flaw in the EmailKit WordPress plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The EmailKit plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to and including 1.6.5. This is due to a flawed path traversal validation in the create_template() method of the CheckForm class, where realpath() is called on the allowed base directory (wp-content/uploads/emailkit/templates/) which may not exist, causing it to return false. In PHP 8.x, strpos($real_path, false) implicitly converts false to an empty string, and strpos() with an empty needle always returns 0, causing the check strpos(...) !== 0 to evaluate to false and bypassing the path validation entirely. This makes it possible for authenticated attackers, with Author-level access and above, to read arbitrary files from the server, including sensitive files such as wp-config.php, by supplying an absolute path to the emailkit-editor-template REST API parameter.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"EmailKit \u003c= 1.6.5 - Authenticated (Author+) Arbitrary File Read via 'emailkit-editor-template' REST Parameter","id":"CVE-2026-5957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Race Condition in GNU Sed","id":"CVE-2026-5958"},"packages":[],"prev":{"headline":"SQLi in Ankara Hosting's Site Management Panel","id":"CVE-2026-5956"},"products":["EmailKit – Email Customizer for WooCommerce \u0026 WP"],"published":"2026-05-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-06","vendors":["roxnor"]},"summary":"Authenticated attackers with Author-level access can read arbitrary files, including wp-config.php, via a path traversal flaw in the EmailKit WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-5957/"}