Wp All ImportWordPress extension · Soflyy
CVE-2018-0546
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 · uneditedCross-site scripting vulnerability in WP All Import plugin prior to version 3.4.6 for WordPress allows an attacker to inject arbitrary web script or HTML via unspecified vectors.
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 the WP All Import WordPress plugin versions prior to 3.4.6 allows unauthenticated attackers to inject malicious JavaScript or HTML into the application. The attack vector is not specified in the advisory, but XSS in WordPress plugins typically stems from insufficient input validation or output escaping in user-facing fields.
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.6CVSS 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 is installedNavigate to WordPress admin > Plugins and locate 'WP All Import' in the list of installed pluginsAffected if Plugin is present in the plugins directory
-
Confirm plugin statusIn the Plugins list, check whether WP All Import shows as 'Active' under the Status columnAffected if Plugin status is Active
-
Determine installed versionClick on the plugin entry or inspect the main plugin file (wp-content/plugins/wp-all-import/plugin.php) and read the Version field from the plugin header commentsAffected if Version number is less than 3.4.6 (for example, 3.4.5 or earlier)
-
Identify exposure to unauthenticated usersSince the vulnerability is described as allowing unauthenticated attackers to inject scripts, check whether the plugin is accessible to non-logged-in visitors through any public-facing features or endpointsAffected if The plugin is accessible to unauthenticated users and the version is below 3.4.6
Environment is affected if WP All Import plugin is installed, active, and running a version lower than 3.4.6.
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 data3.4.6
Update WP All Import plugin to version 3.4.6 or later. If immediate updating is not feasible, consider disabling the plugin until the patch can be applied, as XSS vulnerabilities can lead to session hijacking or credential theft.
Fix this in Wp All Import
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0546 — 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-0546 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