Wp All ImportWordPress extension · Soflyy
CVE-2018-16258
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 pmxi-admin-import custom_type. 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 confidenceCross-site scripting (XSS) vulnerability in WP All Import plugin version 3.4.9 allows injection of malicious scripts via the custom_type parameter in the pmxi-admin-import functionality. The vulnerability is a stored XSS issue that could allow stealing admin session cookies or performing actions with admin privileges.
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 your WordPress plugins directory or admin panel for the presence of the WP All Import plugin by SoflyyAffected if WP All Import is not present in the plugins list, the system is not affected by this specific CVE
-
Confirm the installed version is 3.4.9Locate the plugin version information in your WordPress plugin admin page or check the plugin header in the main plugin fileAffected if The installed version matches 3.4.9 exactly, indicating the vulnerable version is present
-
Verify access to pmxi-admin-import functionalityCheck if the import functionality (pmxi-admin-import) is accessible in the WordPress admin panel under the WP All Import menuAffected if The pmxi-admin-import page is accessible and functional, enabling the attack surface for this vulnerability
-
Check custom_type parameter usageWhen using the import functionality, examine if the custom_type parameter can be controlled through user input in the import configurationAffected if The custom_type parameter accepts user-supplied values without sanitization, creating the conditions for XSS exploitation
If WP All Import version 3.4.9 is installed AND the pmxi-admin-import functionality is accessible with user-controllable custom_type parameter input, the environment is affected by this CVE.
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 on the custom_type parameter to neutralize malicious script injection. While the vendor notes admin access is required, an XSS in an admin-only area still poses risks from privilege escalation and session hijacking.
Fix this in Wp All Import
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.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,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16258 — 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-16258 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