dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-9212

HIGH · 7.5 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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 WP Dispatcher plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the wp_dispatcher_process_upload() function in all versions up to, and including, 1.2.0. 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. The directory does have an .htaccess file which limits the ability to achieve 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 · high confidence

The WP Dispatcher WordPress plugin lacks file type validation in the wp_dispatcher_process_upload() function, allowing authenticated users with Subscriber-level access or higher to upload arbitrary files to the server. While an .htaccess file exists in the upload directory to limit remote code execution, the arbitrary file upload vector remains exploitable.

MitigationUpdate the WP Dispatcher plugin to a version beyond 1.2.0 once a patch is released, or implement server-side file type and extension validation with allowlists in the upload handler. Until patched, disable file upload capabilities for Subscriber-level users.

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

CVSS:3.1/AV:N/AC:H/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. Confirm WP Dispatcher plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'WP Dispatcher' in the installed plugins list, or inspect the file /wp-content/plugins/ directory for a wp-dispatcher folder
    Affected if WP Dispatcher plugin is present in the WordPress installation
  2. Identify installed plugin version
    In Plugins admin page, locate WP Dispatcher and note the version number displayed under the plugin name; alternatively, read the version header in /wp-content/plugins/wp-dispatcher/wp-dispatcher.php
    Affected if Version is 1.2.0 or earlier (no patched version beyond 1.2.0 has been released per the CVE)
  3. Verify upload functionality is accessible
    Check if the wp_dispatcher_process_upload() function exists in the plugin files at /wp-content/plugins/wp-dispatcher/includes/ or similar path, and confirm the upload endpoint is accessible (typically via wp-admin/admin-ajax.php with action=wp_dispatcher_upload or similar)
    Affected if The upload function exists and responds to authenticated requests
  4. Confirm Subscriber-level user existence and role
    In WordPress admin, go to Users > All Users and review roles assigned; check if any users have the Subscriber role, or inspect user capabilities via database or user_edit.php to see if 'upload_files' capability is granted to Subscriber-level accounts
    Affected if Any user with Subscriber role exists and has upload_files capability, or the site accepts Subscriber-level users generally

You are affected if WP Dispatcher plugin version 1.2.0 or earlier is installed AND Subscriber-level users can access the upload functionality.

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 WP Dispatcher plugin to a version beyond 1.2.0 once a patch is released, or implement server-side file type and extension validation with allowlists in the upload handler. Until patched, disable file upload capabilities for Subscriber-level users.

Recommended fix Moderate confidence

Latest version beyond 1.2.0 from wordpress.org/plugins/wp-dispatcher/

  1. Check WordPress admin dashboard for plugin updates for WP Dispatcher
  2. Update WP Dispatcher plugin to the latest available version from the official WordPress plugin repository
  3. Verify the update was successfully applied by checking the plugin version in the installed plugins list
  4. If automatic updates are not enabled, consider enabling them or regularly checking for updates

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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