dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10001

HIGH · 7.2 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The Import any XML, CSV or Excel File to WordPress plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the import functionality in all versions up to, and including, 3.9.3. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload unsafe files like .phar files on the affected site's server which may make remote code execution possible.

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 Import any XML, CSV or Excel File to WordPress plugin fails to validate file types during the import process, allowing authenticated administrators to upload arbitrary files including .phar (PHP Archive) files. Since .phar files can execute PHP code when accessed, this vulnerability enables remote code execution on the affected server.

MitigationUpdate the plugin to version 3.9.4 or later which includes proper file type validation. If immediate updating is not possible, restrict administrator access to trusted personnel and implement file upload monitoring to detect suspicious .phar file uploads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > look for 'Import any XML, CSV or Excel File' and note the version number displayed, or run: wp plugin list --name='wp-all-import' --format=table
    Affected if the installed version is lower than 3.9.4 and the plugin is active
  2. Verify administrator access to import feature
    Log in as an administrator and navigate to the plugin's import functionality (typically under a menu item created by the plugin such as 'All Import' or 'Import')
    Affected if the import feature is accessible and the user has administrator privileges
  3. Confirm .phar file upload capability
    Attempt a test import using a .phar file extension to see if the file type validation allows it through, or check the plugin's allowed file extensions configuration in the WordPress admin
    Affected if the plugin accepts .phar files during import without rejecting them based on file type validation
  4. Check PHP execution settings for uploaded files
    Review the web server and PHP configuration for the upload directory - check if .phar files can be executed as PHP (look for 'phar' in disable_functions and verify AllowUrlInclude is off)
    Affected if .phar files in the upload directory can be directly accessed and executed by the web server

You are affected if the plugin version is below 3.9.4 AND the import feature is accessible to authenticated administrators who can upload .phar files that can then be executed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.9.4 or later which includes proper file type validation. If immediate updating is not possible, restrict administrator access to trusted personnel and implement file upload monitoring to detect suspicious .phar file uploads.

Recommended fix High confidence

Version 3.9.4 or latest stable release

  1. 1. Log in to the WordPress admin dashboard with Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Import any XML, CSV or Excel File to WordPress' (WP All Import) plugin
  4. 4. Check the current installed version in the plugin list
  5. 5. If the installed version is 3.9.3 or lower, click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/wp-all-import/
  6. 6. After updating, verify the new version number reflects the update (e.g., 3.9.4 or later)
  7. 7. Test the import functionality to ensure it still works correctly with legitimate file types (XML, CSV, Excel)
Caveat Minor - verify that existing import templates and scheduled imports still function after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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