dbcve.org
Wp Smart ImportWordPress extension · Xylusthemes

CVE-2024-30201

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.0.5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Xylus Themes WordPress Importer allows Reflected XSS.This issue affects WordPress Importer: from n/a through 1.0.4.

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 confidence

The Xylus Themes WordPress Importer plugin versions up to 1.0.4 contains a reflected cross-site scripting (XSS) vulnerability. User-supplied input is not properly neutralized before being included in the web page output, allowing attackers to inject malicious scripts that execute in the context of the victim's browser.

MitigationUpdate the WordPress Importer plugin to a version beyond 1.0.4 when available, or apply proper input validation and output encoding (escaping) to all user-supplied parameters before they are reflected in HTML responses.

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 Smart ImportWordPress extension
Affected:< 1.0.5

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.1/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 the plugin installation directory
    Access your WordPress server via FTP or file manager and navigate to /wp-content/plugins/ directory. Look for a folder named 'wp-smart-import' or 'wp-smart-import-pro' or similar Xylusthemes plugin folders.
    Affected if The plugin directory exists on the server.
  2. Identify the plugin version from header
    Open the main plugin PHP file (usually the primary PHP file in the plugin folder) and look for the 'Version' field in the plugin header comment block at the top of the file.
    Affected if The version number displayed is less than 1.0.5 (e.g., 1.0.4, 1.0.3, etc.).
  3. Check version via WordPress admin
    Log into WordPress admin dashboard, go to Plugins > Installed Plugins. Locate the Xylusthemes plugin (_wp Smart Import_ or similar) and read the version number displayed beneath the plugin name.
    Affected if The version shown is 1.0.4 or earlier.
  4. Identify accessible parameters
    Review plugin source code for $_GET, $_POST, or $_REQUEST parameters that are reflected in HTML output without proper sanitization (look for echo or print statements containing request parameters).
    Affected if Unsanitized user parameters exist in the code and the plugin is version 1.0.4 or below.

You are affected if the Xylusthemes WordPress Importer plugin is installed and its version is 1.0.4 or lower (anything less than 1.0.5).

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.5 or later
Fixed in 1.0.5
Interim mitigation

Update the WordPress Importer plugin to a version beyond 1.0.4 when available, or apply proper input validation and output encoding (escaping) to all user-supplied parameters before they are reflected in HTML responses.

Recommended fix High confidence

Wp Smart Import version 1.0.5

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find 'Wp Smart Import' (also known as WordPress Importer by Xylus Themes) in the plugin list.
  4. 4. Check if the current installed version is below 1.0.5.
  5. 5. If vulnerable, click 'Update Now' if an update is available, or manually download version 1.0.5 from the WordPress plugin repository.
  6. 6. After updating, verify the plugin version shows 1.0.5 or higher.
  7. 7. Test the plugin functionality to ensure the update did not break existing imports.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Smart Import Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30201 — 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-2024-30201 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