dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-23921

CRITICAL · 9.0 CVSS v3.1 Published 2025-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unrestricted Upload of File with Dangerous Type vulnerability in sh1zen Multi Uploader for Gravity Forms gf-multi-uploader allows Upload a Web Shell to a Web Server.This issue affects Multi Uploader for Gravity Forms: from n/a through <= 1.1.3.

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

An unrestricted file upload vulnerability in the Multi Uploader for Gravity Forms WordPress plugin (gf-multi-uploader) versions 1.1.3 and below allows unauthenticated attackers to upload dangerous file types, including web shells, directly to the web server without proper validation of file types or contents.

MitigationUpdate the plugin to the latest available version immediately. If no patched version exists, disable the plugin entirely and review the server for any already-uploaded malicious files.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 plugin installation and version
    Locate the Multi Uploader for Gravity Forms plugin in your WordPress installation (typically under wp-content/plugins/) and check the main plugin file header for the version number, or view it in the WordPress admin Plugins page.
    Affected if The installed version is 1.1.3 or lower.
  2. Confirm plugin is active
    In WordPress admin, navigate to Plugins and verify that the Multi Uploader for Gravity Forms plugin is currently activated.
    Affected if The plugin is activated and version is 1.1.3 or lower.
  3. Check if Gravity Forms is installed and active
    Verify that Gravity Forms plugin is installed and active, as this plugin extends Gravity Forms functionality.
    Affected if Gravity Forms is active and the Multi Uploader plugin version is 1.1.3 or lower.
  4. Inspect upload directory configuration
    Check the wp-content/uploads/ directory and any custom upload paths configured for the plugin. Look for any recently uploaded files with unexpected extensions such as .php, .phtml, or .exe.
    Affected if The upload directory contains executable files (.php, .phtml, etc.) that were not intentionally uploaded by an administrator.

You are affected if the Multi Uploader for Gravity Forms plugin is installed, active, and running version 1.1.3 or lower, and your upload directory contains unauthorized executable files.

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 the latest available version immediately. If no patched version exists, disable the plugin entirely and review the server for any already-uploaded malicious files.

Recommended fix Moderate confidence

Latest available version of Multi Uploader for Gravity Forms (version higher than 1.1.3)

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'Multi Uploader for Gravity Forms' (by sh1zen) in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest patched version.
  5. 5. After updating, verify the plugin is active and functioning correctly.
  6. 6. Test the file upload functionality to ensure it still works as expected after the update.
  7. 7. Monitor for any unusual files in the wp-content/uploads directory and remove any suspicious PHP files if found.

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-23921 — 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-23921 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