dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-10057

HIGH · 8.8 CVSS v3.1 Published 2025-09-17
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 WP Import – Ultimate CSV XML Importer for WordPress plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 7.28. This is due to the write_to_customfile() function writing unfiltered PHP code to a file. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject the customFunction.php file with PHP code that can be accessed to trigger remote code execution.

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

The WP Import plugin for WordPress contains an RCE vulnerability in its write_to_customfile() function, which writes unfiltered PHP code to customFunction.php. Attackers with minimal subscriber-level privileges can inject arbitrary PHP code that gets executed when the file is accessed, achieving full remote code execution on the affected WordPress installation.

MitigationUpdate the plugin to a version beyond 7.28 if a patched version is available; otherwise, disable the plugin immediately. Restrict PHP execution in upload directories and review user role permissions as compensating controls.

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. Identify the plugin and its installed version
    Check the plugin's main PHP file header for the 'Version' field, typically found in wp-content/plugins/wp-import-ultimate-csv-xml-importer/ or similar plugin directory name. You can also check via WordPress admin under Plugins > Installed Plugins.
    Affected if The version listed is 7.28 or lower (any version 'up to 7.28' is affected)
  2. Locate the customFunction.php file
    Search the plugin directory for a file named customFunction.php, typically found within the plugin's includes or helpers subdirectories where custom import functions are stored.
    Affected if The file exists in the plugin directory, indicating the vulnerable function is present
  3. Inspect the customFunction.php file contents
    Open customFunction.php in a text editor or via command line and examine its contents. Look for any PHP code that was not part of the original plugin release, such as base64_decode(), eval(), shell_exec(), system(), or suspicious variable assignments.
    Affected if The file contains unfamiliar or malicious-looking PHP code that you did not intentionally add, suggesting exploitation has occurred
  4. Verify WordPress user role configuration
    In WordPress admin, go to Users > All Users and review the role assigned to low-privilege accounts. Check if any Subscriber-level or higher users exist who should not have author-level access.
    Affected if There are Subscriber-level or higher users (especially those you do not recognize) who could trigger the vulnerable code path
  5. Check web server access logs for requests to customFunction.php
    Review your web server access logs (Apache, Nginx, or equivalent) for any GET or POST requests to the path containing customFunction.php, especially from authenticated user sessions.
    Affected if Requests to customFunction.php appear in logs from users who should not have needed that functionality, indicating active probing or exploitation

You are affected if the plugin version is 7.28 or lower and the customFunction.php file exists in the plugin directory, regardless of whether it shows signs of compromise.

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

Update the plugin to a version beyond 7.28 if a patched version is available; otherwise, disable the plugin immediately. Restrict PHP execution in upload directories and review user role permissions as compensating controls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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