dbcve.org
Wp Smart ImportWordPress extension · Xylusthemes

CVE-2025-47453

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 1.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Xylus Themes WP Smart Import wp-smart-import allows PHP Local File Inclusion.This issue affects WP Smart Import: from n/a through <= 1.1.3.

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

Local File Inclusion vulnerability in WP Smart Import plugin allows attackers to control filenames used in PHP include/require statements, potentially enabling arbitrary PHP code execution on the server.

MitigationUpdate to the latest version of WP Smart Import if available, or disable the plugin until a patch is released. If exploitation is suspected, conduct a forensic review of the server for compromised files.

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.1.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check if WP Smart Import plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Smart Import' or 'Wp Smart Import' by Xylusthemes. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-smart-import' or similar.
    Affected if The plugin is present on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WP Smart Import and view the version number displayed. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment block.
    Affected if The installed version is less than 1.1.4 (or if the version cannot be determined but the plugin is present)
  3. Verify the vulnerable file inclusion functionality
    Examine plugin source files for includes/requires that use user-controlled parameters. Look for PHP include(), require(), require_once(), or include_once() statements where a request parameter (like $_GET, $_POST) is used in the path. Check files in the admin/ or includes/ folders of the plugin.
    Affected if The plugin contains include/require statements that incorporate request parameters without proper sanitization
  4. Check for unauthorized or suspicious PHP files
    Review /wp-content/uploads/ and /wp-content/plugins/ directories for newly created PHP files with random names, encoded content, or files matching patterns like 'cache', 'temp', or 'shell'. Use file integrity monitoring if available.
    Affected if Unexpected PHP files exist that were not deployed by the administrator

A WordPress site is affected if the WP Smart Import plugin is installed with a version lower than 1.1.4 and the vulnerable file inclusion code path is accessible to attackers.

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.1.4 or later
Fixed in 1.1.4
Interim mitigation

Update to the latest version of WP Smart Import if available, or disable the plugin until a patch is released. If exploitation is suspected, conduct a forensic review of the server for compromised files.

Recommended fix Moderate confidence

WP Smart Import version 1.1.4

  1. Backup your WordPress site database and files before proceeding
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find WP Smart Import in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.1.4 of the plugin
  5. Verify the plugin version shows 1.1.4 after updating
  6. Test that the plugin functionality works as expected

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

Fix this in Wp Smart Import Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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