CVE-2026-13430
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Post Export Import with Media WordPress plugin fails to properly validate file extensions when processing imported ZIP files. Attackers can bypass the allow-list check by adding a trailing dot to filenames (e.g., 'shell.php.'), causing pathinfo() to return an empty extension string that passes the validation guard. The subsequent copy operation in import_media_file_secure() does not re-validate the extension, allowing executable PHP files to be uploaded to the uploads directory for remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check plugin version in WordPress adminNavigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Post Export Import with Media' and note the version number displayed under the plugin name.Affected if The installed version is lower than 1.14.0 (the version that contains the fix for the trailing-dot bypass).
-
Identify if import functionality is accessibleVerify that the plugin's import feature is available and accessible. Check if the user has permissions to access the import Media function (usually under the plugin's settings or Tools menu).Affected if The import functionality is accessible to users with administrative or editor-level permissions, and the plugin version is below 1.14.0.
-
Scan uploads directory for files with trailing dotsUse a file manager or command line to list files in wp-content/uploads/ and its subdirectories. Search for filenames ending with a dot followed by a known extension (e.g., shell.php., malicious., backdoor.). On Linux: find /path/to/wp-content/uploads/ -name '*.php.' -o -name '*.' | head -50Affected if Any .php files (or other executable extensions) are found with trailing dots in the filenames within the uploads directory, indicating attempted exploitation.
-
Review recent upload activity logsCheck WordPress activity logs, server access logs, or the plugin's own logging (if available) for recent import operations. Look for entries involving ZIP file imports.Affected if Import operations involving ZIP files were performed recently and the plugin version is below 1.14.0.
A user is affected if the Post Export Import with Media plugin version is below 1.14.0 and the import functionality has been used, or if suspicious files with trailing dots exist in the uploads directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 1.14.0 or later which addresses the trailing-dot bypass. If immediate upgrade is not possible, restrict administrator-level user creation and monitor uploads for files with unusual extensions or trailing dots.
Latest version of Post Export Import with Media plugin (version higher than 1.13.1)
- 1. Log in to WordPress admin dashboard with administrator-level access
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Post Export Import with Media' plugin in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to the latest version
- 5. After updating, verify the new version number is higher than 1.13.1
- 6. Test the import functionality to ensure the plugin continues to work correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13430 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13430 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data