Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& CsvWordPress extension · Smackcoders
CVE-2018-20967
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-ultimate-csv-importer plugin before 5.6.1 for WordPress has CSRF.
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 · moderate confidenceThe wp-ultimate-csv-importer plugin before version 5.6.1 for WordPress contains a Cross-Site Request Forgery (CSRF) vulnerability. Attackers can exploit this by tricking authenticated administrators into clicking malicious links or visiting crafted pages, causing the browser to send forged requests that perform unwanted actions within the plugin (such as importing data or modifying settings).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& CsvWordPress extension
< 5.6.1CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'wp-ultimate-csv-importer' or 'Smackcoders Import All Pages, Post Types, Products, Orders, And Users As Xml & Csv' in the listAffected if The plugin does not appear in the installed plugins list
-
Check plugin versionOn the Plugins page, locate the plugin and hover over or click to view the version number, or read the main plugin file (wp-content/plugins/wp-ultimate-csv-importer/wp-ultimate-csv-importer.php) and look for the 'Version' header in the plugin commentsAffected if The displayed version is lower than 5.6.1 (for example, 5.6.0, 5.5.0, etc.)
-
Verify plugin is activeOn the WordPress Plugins > Installed Plugins page, check if the plugin shows as 'Active' (the plugin must be active for the CSRF to be exploitable)Affected if The plugin is activated and running on the site
If the wp-ultimate-csv-importer plugin is installed, active, and its version is below 5.6.1, the site is vulnerable to CVE-2018-20967 CSRF attacks targeting authenticated administrators.
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 data5.6.1
Update the wp-ultimate-csv-importer plugin to version 5.6.1 or later, which includes proper anti-CSRF token validation (nonces) to verify request origin and authenticity.
Fix this in Import All Pages\, Post Types\, Products\, Orders\, And Users As Xml \& Csv
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20967 — 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-2018-20967 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