dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-14344

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'plupload_ajax_delete_file' function in all versions up to, and including, 1.1.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server.

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 Multi Uploader for Gravity Forms WordPress plugin contains an unauthenticated arbitrary file deletion vulnerability in the plupload_ajax_delete_file function. Due to insufficient path validation, attackers can use directory traversal sequences to delete any file on the server accessible to the web server process.

MitigationUpdate the plugin to version 1.1.8 or later where the vulnerability is patched. If no patched version is available, disable or remove the plugin immediately.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin is installed
    Check if the Multi Uploader for Gravity Forms plugin exists in the WordPress plugins directory (wp-content/plugins/multi-uploader-for-gravity-forms/ or similar path) or view the installed plugins list in WordPress admin under Plugins
    Affected if Plugin directory or listing exists in the WordPress installation
  2. Identify installed version
    Open the main plugin PHP file and look for the 'Version' header comment in the plugin file headers, or check the WordPress plugin admin page which displays version numbers
    Affected if Version number is lower than 1.1.8 or cannot be determined (treated as vulnerable)
  3. Verify the vulnerable function exists
    Locate the plupload_ajax_delete_file function in the plugin's PHP files (typically in the main plugin file or an ajax handler file) and examine if it uses user-supplied input for file paths without proper sanitization
    Affected if Function exists and uses $_POST or $_GET parameters directly for file deletion without validate the path is within the uploads directory
  4. Check if WordPress ajax endpoint is accessible
    Verify the wp-admin/admin-ajax.php endpoint responds to the plugin's ajax action (usually named 'plupload_delete_file' or similar), which can be tested by checking if the action is registered in the plugin code
    Affected if The ajax action for file deletion is registered and the endpoint is reachable without authentication (unauthenticated access)
  5. Look for signs of exploitation
    Review web server access logs for unusual delete requests to admin-ajax.php with the plugin's delete action, checking for patterns like '../' path traversal sequences in the parameters
    Affected if Logs show requests with path traversal patterns (../) targeting the delete function

The environment is affected if the Multi Uploader for Gravity Forms plugin is installed with a version lower than 1.1.8 and the plupload_ajax_delete_file function is accessible, allowing unauthenticated path traversal deletion of arbitrary 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 version 1.1.8 or later where the vulnerability is patched. If no patched version is available, disable or remove the plugin immediately.

Recommended fix Moderate confidence

Version 1.1.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Multi Uploader for Gravity Forms' plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/multi-uploader-for-gravity-forms/
  6. Verify the updated version is at least 1.1.8

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