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.
CVE-2026-13430
HIGHPre-NVD 7.27.2—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 7.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.2Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EPSS
- 45.3%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/post-export-import-with-media/tags/1.13.1/includes/class-media-handler.php#L268
- security@wordfencehttps://plugins.trac.wordpress.org/browser/post-export-import-with-media/tags/1.13.1/includes/class-media-handler.php#L364
- security@wordfencehttps://plugins.trac.wordpress.org/browser/post-export-import-with-media/tags/1.13.1/includes/class-media-handler.php#L389
- security@wordfencehttps://plugins.trac.wordpress.org/browser/post-export-import-with-media/tags/1.13.1/includes/class-media-handler.php#L444
- security@wordfencehttps://plugins.trac.wordpress.org/browser/post-export-import-with-media/tags/1.13.1/includes/class-media-handler.php#L789
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3600506%40post-export-import-with-media&new=3600506%40post-export-import-with-media
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/42f94f80-6157-4778-ad69-184943134fd2?source=cve
Vendor Advisories for CVE-2026-13430(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 03:02 UTCEG score recompute
- 2026-07-15 03:02 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 15:07 UTCEG score recompute
- 2026-07-14 15:07 UTCGHSA enrichment
- 2026-07-14 03:11 UTCEG score recompute
- 2026-07-14 03:11 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 15:16 UTCEG score recompute
- 2026-07-13 15:15 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 03:20 UTCEG score recompute
- 2026-07-13 03:20 UTCGHSA enrichment
- 2026-07-12 15:25 UTCEG score recompute
- 2026-07-12 15:25 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:29 UTCEG score recompute
- 2026-07-12 03:29 UTCGHSA enrichment
- 2026-07-11 15:34 UTCEG score recompute
- 2026-07-11 15:34 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:39 UTCEG score recompute
- 2026-07-11 03:39 UTCGHSA enrichment
- 2026-07-10 15:45 UTCEG score recompute
- 2026-07-10 15:44 UTCGHSA enrichment
Show 2 moreShow fewer
- 2026-07-10 03:49 UTCEG score recompute
- 2026-07-10 03:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-434
Frequently asked(5)
What is CVE-2026-13430?
CVE-2026-13430 is a high vulnerability published on July 10, 2026. 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 importmediafilesecure function. This is due to insufficient file extension validation caused by a trailing-dot filename bypass, where the extension…
When was CVE-2026-13430 disclosed?
CVE-2026-13430 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13430 actively exploited?
CVE-2026-13430 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13430?
CVE-2026-13430 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-13430?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13430, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13430
Is Your Infrastructure Affected by CVE-2026-13430?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.