WordPress Importer
WordPress Importer has one disclosed vulnerability in the WordSec catalog, all reported in 2025; it is fixed as of September 2026. Their average CVSS score is 7.2, and the most serious one scores 7.2 out of 10. Severity breakdown: 0 critical and 1 high.
The most common weakness is Deserialization Of Untrusted Data, behind 1 of the records (100%).
The one issue recorded for WordPress Importer has a vendor fix available, so running the current release closes it.
All of these findings were reported by Francesco Carlucci. WordPress Importer is installed on roughly 2,000,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.8.8.
CVE-2024-13889WordPress Importer <= 0.8.3 - Authenticated (Administrator+) PHP Object Injection
Read the full analysisVulnerability Records
WordPress Importer
Author
WordPress.org
The WordPress Importer will import the following content from a WordPress export file: Posts, pages and other custom post types Comments and comment meta Custom fields and post meta Categories, tags and terms from custom taxonomies and term meta Authors For further information and instructions please see the documention on Importing Content. Filters The importer has a couple of filters to allow you to completely enable/block certain features: import_allow_create_users: return false if you only want to allow mapping to existing users import_allow_fetch_attachments: return false if you do not wish to allow importing and downloading of attachments import_attachment_size_limit: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited) There are also a few actions available to hook into: import_start: occurs after the export file has been uploaded and author import settings have been chosen import_end: called after the last output from the importer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C