dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-5740

HIGH · 7.2 CVSS v3.1 Published 2025-06-10
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
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause arbitrary file writes when an authenticated user on the web server manipulates file path.

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 · moderate confidence

This is a path traversal vulnerability (CWE-22) in a web server application that allows an authenticated user to manipulate file paths and write files to arbitrary locations on the system. The vulnerability stems from insufficient validation of user-supplied file paths, enabling attackers to escape the intended restricted directory and write files outside the expected boundary.

MitigationImplement strict input validation with allowlist filtering, use secure path normalization functions to resolve and verify the canonical path stays within allowed directories, and restrict file write operations to explicitly defined safe directories.

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 the web server application and version
    Review your server documentation, running processes, or application headers (e.g., check HTTP Server header, examine installed packages) to determine the exact application name and installed version. Compare this version against any publicly available advisory for CVE-2025-5740.
    Affected if The application version falls within the affected range stated in the CVE advisory.
  2. Confirm file upload or write functionality is exposed
    Examine your web server configuration and running endpoints to determine if file upload, file save, or file write features are accessible. Check for URLs or API endpoints that accept file path parameters (e.g., endpoints handling filenames, paths, or upload operations).
    Affected if File upload, file save, or file write endpoints are accessible and operational on the server.
  3. Verify authentication is enabled for the application
    Review the application authentication settings, session management configuration, and user access controls. Confirm whether the application requires valid credentials for accessing file-related functions.
    Affected if The application allows authenticated access to file operations, as the CVE requires an authenticated user to exploit the path traversal.
  4. Check file operation permissions
    Inspect the application's user and group permissions on the filesystem. Determine whether the web server process runs with write access to directories outside the intended upload or working directory.
    Affected if The application process has write permissions to directories beyond its intended restricted upload folder.
  5. Review access logs for suspicious path patterns
    Examine web server access logs for requests containing path traversal patterns such as '../', '..\', or absolute paths in file upload or path parameters. Look for anomalies indicating exploitation attempts.
    Affected if Logs show requests with traversal sequences targeting directories outside the expected upload boundary.

Your environment is likely affected if you run a web server application with file upload or write functionality, the application allows authenticated access, and it runs with permissions that permit writing outside the intended restricted directory.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation with allowlist filtering, use secure path normalization functions to resolve and verify the canonical path stays within allowed directories, and restrict file write operations to explicitly defined safe directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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