Is my WordPress plugin safe?

• Oct 17, 2026Post Export Import with Media: Directory TraversalCVE-2026-110268 · affects up to 1.17.2 · reported by WordfenceMedium 4.9

  The Post Export Import with Media plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.17.2 via the 'theme_slug' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to perform actions on files outside of the originally intended directory. Exploitation requires the peiwm_enable_admin_download_buttons feature to be enabled in the plugin settings.

  NVD recordplugins.svn.wordpress.orgplugins.trac.wordpress.org

• Oct 14, 2026Post Export Import with Media: PHP Object InjectionCVE-2026-104764 · affects up to 1.17.1 · reported by WordfenceHigh 7.2

  The Post Export Import with Media plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.17.1 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

  NVD recordplugins.svn.wordpress.orgplugins.trac.wordpress.org

• Oct 10, 2026Post Export Import with Media: Directory TraversalCVE-2026-104763 · affects up to 1.17.1 · reported by WordfenceMedium 4.9

  The Post Export Import with Media plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.17.1 via the 'file_path' parameter parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. This requires the attacker to upload a crafted ZIP archive containing a media_metadata.json file with path traversal sequences in the file_path field while specifying an allowed file extension for the destination filename to bypass the extension guard introduced in version 1.13.2.

  NVD recordplugins.svn.wordpress.orgplugins.trac.wordpress.org

• Jul 10, 2026Post Export Import with Media: Arbitrary File UploadCVE-2026-13430 · affects up to 1.13.1 · reported by WordfenceHigh 7.2

  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.

  NVD recordplugins.trac.wordpress.orgplugins.trac.wordpress.org

Versions are matched against the affected ranges published with each record. A plugin can ship a fix under its own numbering, so if something looks off, check the linked record. Want the whole site checked at once? Run the free website check.