dbcve.org
Wp All ImportWordPress extension · Soflyy

CVE-2018-0547

MEDIUM · 6.1 CVSS v3.0 Published 2018-03-09
Fix available
A fix is available. Upgrade to after 3.4.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting vulnerability in WP All Import plugin prior to version 3.4.7 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 confidence

Cross-site scripting (XSS) vulnerability in WP All Import plugin versions prior to 3.4.7 for WordPress allows authenticated or unauthenticated attackers to inject malicious JavaScript or HTML into web pages viewed by other users, potentially leading to session hijacking or credential theft.

MitigationUpdate WP All Import plugin to version 3.4.7 or later to remediate the XSS vulnerability. Review user roles and permissions in WordPress admin.

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
Affected:<= 3.4.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate WP All Import plugin files
    Check the /wp-content/plugins/ directory for the 'wp-all-import' folder, or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists and the plugin is installed
  2. Identify installed version
    In WordPress admin, find WP All Import in the plugins list and note the version number displayed, or open the main plugin file (typically wp-all-import.php) and look for the 'Version' header comment
    Affected if Version listed is 3.4.6 or lower (any version prior to 3.4.7)
  3. Determine if plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify whether WP All Import shows as 'Active'
    Affected if Plugin is active and accessible to users on the site

If WP All Import version 3.4.6 or lower is installed and active, the site is vulnerable to XSS attacks via this plugin.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.4.6
Interim mitigation

Update WP All Import plugin to version 3.4.7 or later to remediate the XSS vulnerability. Review user roles and permissions in WordPress admin.

Fix this in Wp All Import Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0547 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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