CVE-2025-13145
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 WP Import – Ultimate CSV XML Importer for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.33.1. This is due to deserialization of untrusted data supplied via CSV file imports in the import_single_post_as_csv function within SingleImportExport.php. This makes it possible for authenticated attackers, with administrator-level access or higher, to inject a PHP object. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
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 WP Import plugin for WordPress is vulnerable to PHP Object Injection due to unsafe deserialization of data from CSV file imports in the import_single_post_as_csv function. Authenticated administrators can inject PHP objects via crafted CSV data, which if a POP chain exists from another plugin/theme, can lead to arbitrary file deletion, data exfiltration, or 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.
-
Verify WP Import plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'WP Import' in the list. Note the version number displayed.Affected if The plugin is installed and the version shown is below 7.33.2 (or version cannot be determined and the plugin is present).
-
Check admin access to import functionalityLog in as an administrator and navigate to the WP Import plugin settings or tools section. Attempt to locate the CSV import feature, typically found under Tools > Import or a dedicated WP Import menu item.Affected if The import_single_post_as_csv function is accessible to administrator-level users.
-
Inspect plugin version file directlyAccess the WordPress wp-content/plugins/wp-import directory via FTP or file manager. Open the main plugin PHP file (usually wp-import.php or similar) and locate the version constant or header comment that declares the plugin version.Affected if The version declared in the plugin header is 7.33.1 or lower, or no version is declared and the plugin file predates the fix.
-
Search for vulnerable unserialize callWithin the plugin directory, search the source code for the string 'unserialize' within the file containing the import_single_post_as_csv function, or grep for 'unserialize' across all plugin PHP files.Affected if An unserialize() call is found processing CSV import data without prior sanitization or JSON replacement.
You are affected if the WP Import plugin is installed, you are running version 7.33.1 or lower, and administrators have access to the CSV import feature.
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.
From vendor dataReplace unsafe unserialize() calls with json_decode() in the import_single_post_as_csv function, validate all imported data, and apply the latest vendor patch (version 7.33.2 or higher).
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13145 — 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-2025-13145 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