dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-69379

HIGH · 8.6 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in vanquish Upload Files Anywhere wp-upload-files-anywhere allows Path Traversal.This issue affects Upload Files Anywhere: from n/a through <= 2.8.

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 vanquish Upload Files Anywhere WordPress plugin (wp-upload-files-anywhere) versions through 2.8 contains a path traversal vulnerability that allows attackers to manipulate file paths using '../' sequences to access files outside the intended upload directory. This improper limitation of pathnames to restricted directories can expose sensitive system files and configurations.

MitigationUpdate the plugin to the latest version when available; if no patch exists, disable the plugin until fixed and implement input validation on file path parameters to prevent directory traversal sequences.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 the vanquish Upload Files Anywhere plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) for a folder named 'wp-upload-files-anywhere' or search for 'vanquish' or 'Upload Files Anywhere' in the installed plugins list via WordPress admin or database
    Affected if The plugin folder 'wp-upload-files-anywhere' exists in the plugins directory
  2. Determine the installed plugin version
    Open the main plugin file (usually wp-upload-files-anywhere.php) or the readme.txt file in the plugin folder and locate the Version header
    Affected if The version listed is 2.8 or lower (any version through 2.8 is affected)
  3. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins' to see if the plugin is enabled
    Affected if The plugin is currently active and the version is 2.8 or lower
  4. Confirm the upload functionality is accessible
    Check if the plugin's upload endpoint or functionality is publicly accessible or accessible to users with upload permissions by reviewing the plugin's settings and any exposed AJAX actions or frontend forms
    Affected if The file upload feature is enabled and accessible to unauthenticated or low-privileged users

You are affected if the vanquish Upload Files Anywhere plugin (wp-upload-files-anywhere) versions 2.8 or lower is installed and active with its upload functionality exposed.

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 version when available; if no patch exists, disable the plugin until fixed and implement input validation on file path parameters to prevent directory traversal sequences.

Recommended fix Moderate confidence

Latest version available (version 2.9 or later) - verify exact version number from WordPress plugin repository

  1. Check the WordPress plugin repository or contact the plugin vendor to confirm if version 2.9 or later contains the security fix for this path traversal vulnerability
  2. If a newer version is available, navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Deactivate the Upload Files Anywhere plugin before updating
  4. Update the plugin to the latest available version
  5. After updating, verify the plugin settings and test that file uploads still work as expected
  6. Review any uploaded files to ensure they are being stored in the intended directory and not outside the wp-content uploads folder

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