dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-2008

HIGH · 8.8 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Export Suite for CSV and XML Datafeed plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the import_single_post_as_csv() function in all versions up to, and including, 7.19. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. Please note this vulnerability was reintroduced in 7.20, and subsequently patched again in 7.20.1.

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 Export Suite for CSV and XML Datafeed WordPress plugin fails to validate file types in the import_single_post_as_csv() function, allowing authenticated users with Subscriber-level permissions to upload arbitrary files to the server. This unrestricted file upload capability enables remote code execution.

MitigationUpdate the plugin to version 7.20.1 or later to patch the arbitrary file upload vulnerability. Consider reviewing user access permissions and monitoring for suspicious 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify the plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Import Export Suite for CSV and XML Datafeed' is installed and active
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the plugin and view the version number. Compare it to the fixed version 7.20.1 - versions before 7.20.1 are vulnerable
    Affected if The installed version is lower than 7.20.1
  3. Verify user role permissions
    Go to WordPress admin > Users > Roles and Permissions, or check if Subscriber-level user accounts exist. The vulnerability allows any authenticated user with Subscriber role to exploit the file upload
    Affected if Subscriber-level or higher user accounts exist on the site and the plugin version is below 7.20.1
  4. Inspect the vulnerable function
    Access the plugin files via FTP or file manager, locate the file containing import_single_post_as_csv() function, and check if it performs file type validation. The function should validate file MIME types before processing uploads
    Affected if The function lacks proper file type validation and the plugin version is below 7.20.1
  5. Review recent upload activity
    Check the wp-content/uploads directory and server access logs for any unexpected file uploads, especially PHP files or executable scripts uploaded around the time the vulnerable plugin was active
    Affected if Suspicious files exist in upload directories that were not intentionally placed there

A user is affected if the Import Export Suite plugin is installed with a version lower than 7.20.1 and the site has user accounts with Subscriber-level or higher permissions, allowing the arbitrary file upload vulnerability to be exploited.

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 7.20.1 or later to patch the arbitrary file upload vulnerability. Consider reviewing user access permissions and monitoring for suspicious file uploads.

Recommended fix High confidence

7.20.1

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'Import Export Suite for CSV and XML Datafeed' plugin
  4. Click 'Update now' to install version 7.20.1, or manually download and upload version 7.20.1 from the WordPress plugin repository
  5. Verify the plugin version shows 7.20.1 after updating
  6. Test the import functionality to confirm the plugin still works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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