dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10051

HIGH · 7.2 CVSS v3.1 Published 2025-10-15
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 Demo Import Kit plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in all versions up to, and including, 1.1.0 via the import functionality. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary 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 Demo Import Kit WordPress plugin lacks file type validation in its import functionality, allowing authenticated administrators to upload arbitrary files to the server. This can include malicious PHP files leading to remote code execution.

MitigationUpdate the plugin to a version beyond 1.1.0 that implements proper file type validation and sanitization, or remove the plugin if no patched version is available.

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. Identify if Demo Import Kit plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named demo-import-kit, demo-import-kit-lite, or similar. Alternatively, list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if The plugin folder exists in wp-content/plugins/ and shows as active in WordPress
  2. Determine the installed plugin version
    Open the plugin's main PHP file (usually in the plugin folder root) and locate the version comment/header, or check the readme.txt file for the Version: field
    Affected if The version is 1.1.0 or lower, or if no version can be determined but the plugin is present
  3. Verify the import functionality is accessible
    Log into WordPress as an administrator and navigate to the plugin settings page (typically under Appearance > Demo Import or a dedicated plugin admin menu). Look for import/upload functionality
    Affected if The import feature is visible and accessible to the administrator account
  4. Check for unexpected uploaded files
    Inspect the WordPress uploads directory (wp-content/uploads/) and the plugin directory for any .php files, .exe files, or scripts that were not intentionally placed there. Use: find wp-content/uploads -name '*.php' 2>/dev/null
    Affected if Unexpected PHP files or other executable scripts are found in uploads or plugin directories, indicating possible exploitation

A user is affected if the Demo Import Kit plugin is installed with version 1.1.0 or lower and the import feature is accessible to administrator accounts, as the lack of file type validation allows arbitrary file uploads.

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 a version beyond 1.1.0 that implements proper file type validation and sanitization, or remove the plugin if no patched version is available.

Recommended fix Moderate confidence

1.1.1 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Demo Import Kit' plugin
  4. Check if an update is available - if so, update to the latest version
  5. If no update is shown in WordPress, manually download the latest version from wordpress.org/plugins/demo-import-kit and upload/install it
  6. Verify the updated version is 1.1.1 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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