Wp All ImportWordPress extension · Soflyy
CVE-2018-16254
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 · uneditedThere is an XSS vulnerability in WP All Import plugin 3.4.9 for WordPress via action=options. NOTE: The vendor states that this is not a vulnerability. WP All Import is only able to be used by a logged in administrator, and the action described can only be taken advantage of by a logged in administrator
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 confidenceStored XSS vulnerability in WP All Import plugin 3.4.9 for WordPress via the action=options parameter. However, the vendor correctly notes that exploitation requires a logged-in administrator with full site access, limiting the actual security impact since an attacker with admin credentials already has complete control of the WordPress installation.
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
Wp All ImportWordPress extension
= 3.4.9CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 All Import plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the wp-all-import folderAffected if The plugin folder wp-all-import exists in the plugins directory
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for WP All Import version number, or check the plugin main file header for 'Version: 3.4.9'Affected if Installed version is exactly 3.4.9
-
Confirm plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify WP All Import shows as 'Active'Affected if Plugin is active and version 3.4.9 is installed
-
Verify admin access existsReview WordPress user roles to confirm if any user accounts have Administrator role, or check wp_users table for user_level 10 or caps containing administratorAffected if Administrator-level accounts exist in the WordPress installation (required for exploitation)
-
Check for suspicious admin actionsReview server access logs for requests to /wp-admin/admin.php?action=options with unusual parameter values, or check WordPress activity logs for XSS payloadsAffected if Evidence of malicious requests to the vulnerable options endpoint
You are affected if WP All Import version 3.4.9 is installed and active, and your site has administrator accounts (the vulnerability requires admin-level access to trigger).
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 dataSince exploitation requires administrator-level access, the primary remediation is ensuring strong administrator account security. Consider updating to the latest plugin version and implementing output escaping on any user-controlled input even in admin areas as a defense-in-depth measure.
Fix this in Wp All Import
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16254 — 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-16254 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