Wp All ImportWordPress extension · Soflyy
CVE-2018-16255
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=evaluate. 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 · moderate confidenceCross-site scripting (XSS) vulnerability in WP All Import plugin version 3.4.9 for WordPress via the action=evaluate parameter. The vulnerability allows injection of malicious scripts through unsanitized user input, which could execute in an administrator's browser session.
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 installedCheck the WordPress plugins directory or access the Plugins page in wp-admin to confirm WP All Import is present and activeAffected if WP All Import plugin is installed and active on the WordPress site
-
Check installed plugin versionNavigate to Plugins > Installed Plugins > WP All Import and locate the version number displayed below the plugin name, or inspect the plugin header in /wp-content/plugins/wp-all-import/plugin.php for 'Version: 3.4.9'Affected if The installed version is exactly 3.4.9
-
Confirm evaluate action is accessibleCheck if the wp_all_import_importer endpoint or similar route handling the action=evaluate parameter exists on the site; this is typically found in the plugin's routing configurationAffected if The evaluate action endpoint is accessible and the plugin handles the action parameter
-
Verify admin access to the vulnerable featureConfirm whether the WordPress user accessing the plugin has administrative privileges; the vulnerability is triggered when an admin interacts with the evaluate functionalityAffected if An authenticated administrator can access the evaluate action with unsanitized input
A site is affected if WP All Import version 3.4.9 is installed and the evaluate action parameter feature is accessible to administrators, allowing unsanitized input to be processed.
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 dataImplement proper input sanitization and output encoding for the evaluate action parameter. While the vendor claims this requires admin access, XSS in admin panels can lead to session hijacking, privilege escalation, or malicious administrative actions and should be remediated.
Fix this in Wp All Import
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16255 — 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-16255 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