{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13430 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13430 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13430 is a high-severity vulnerability in wpazleen Post Export Import with Media, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-13430 and fix it if it is affected.\n\nWhat it is: CVE-2026-13430 is a high-severity vulnerability in wpazleen Post Export Import with Media, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-13430 in the wild and no public exploit code.\n\nAffected product: wpazleen Post Export Import with Media. 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-13430/ (Markdown: https://insights.sbomify.com/CVE-2026-13430/index.md)","id":"CVE-2026-13430","markdown":"https://insights.sbomify.com/CVE-2026-13430/index.md","name":"CVE-2026-13430","record":{"aliases":["GHSA-mxq7-wpp5-2fc9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can upload executable files via a trailing-dot filename bypass in the ZIP import feature, leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The Post Export Import with Media plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 1.13.1 via the import_media_file_secure function. This is due to insufficient file extension validation caused by a trailing-dot filename bypass, where the extension allow-list check in ajax_import_media_start() uses pathinfo() on the raw ZIP entry name (e.g., 'shell.php.'), which returns an empty string for the extension, causing the allow-list guard to be skipped and the file to be extracted to a temporary location, after which import_media_file_secure() copies it into the WordPress uploads directory without re-validating the extension. This makes it possible for authenticated attackers, with administrator-level access and above, to upload files that may be executable, which makes remote code execution possible.","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":"File upload in Post Export Import with Media","id":"CVE-2026-13430","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ThumbPress \u003c 6.2.2 - Subscriber+ Plugin Deactivation","id":"CVE-2026-13432"},"packages":[],"prev":{"headline":"Client4 fails to validate path parameters","id":"CVE-2026-13426"},"products":["Post Export Import with Media"],"published":"2026-07-10","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":"total"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["wpazleen"]},"summary":"Authenticated administrators can upload executable files via a trailing-dot filename bypass in the ZIP import feature, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2026-13430/"}