highCVE-2026-13430

Post Export Import with Media <= 1.13.1 - Authenticated (Administrator+) Arbitrary File Upload via Trailing-Dot Filename Bypass in ZIP Media Import

Q: What is affected by CVE-2026-13430?

Post Export Import with Media versions listed as affected should be reviewed: *-1.13.1.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

ProductPost Export Import with Media

CVSS7.2

EPSS0.00615

UpdatedJuly 13, 2026

Quick answer

Post Export Import with Media should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-1.13.1

Fixed versions

1.13.2

How to fix it

Post Export Import with Media is affected by CVE-2026-13430, a unsafe file upload issue in versions up to 1.13.1. Wordfence lists the official remediation as updating to version 1.13.2, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Post Export Import with Media installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
Confirm the installed Post Export Import with Media version and compare it with the affected range from the Wordfence advisory.
Update Post Export Import with Media to version 1.13.2, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Post Export Import with Media or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Inspect upload directories, plugin storage paths, media folders, backups, snippets, and recently modified files for unexpected scripts, deleted files, webshells, or executable content.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, booking/support plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running Post Export Import with Media version is version 1.13.2 or newer, and record the patched version in the remediation ticket.
Verify unsafe file types cannot be uploaded or executed from user-writable paths after the update or mitigation.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress PHP Remote Code Execution File Upload Arbitrary File Write

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-13430?

Post Export Import with Media versions listed as affected should be reviewed: *-1.13.1.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.