CVE-2025-66206
BaseFortify
Publication date: 2025-12-01
Last updated on: 2025-12-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| frappe | frappe | to 14.99.2 (exc) |
| frappe | frappe | From 15.0.0 (inc) to 15.86.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a path traversal issue in the Frappe web application framework versions prior to 15.86.0 and 14.99.2. It allows an attacker to retrieve certain files from the server if they know the full path to those files. The vulnerability mainly affects setups that use werkzeug/gunicorn directly without a reverse proxy like NGINX. Sites hosted on Frappe Cloud or behind a reverse proxy are not affected.
How can this vulnerability impact me? :
If you are using Frappe without a reverse proxy and have not upgraded to versions 15.86.0 or 14.99.2 or later, an attacker could exploit this vulnerability to access sensitive files on your server by knowing their full path. This could lead to exposure of confidential information. Using a reverse proxy or upgrading the framework mitigates this risk.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Frappe to version 15.86.0 or 14.99.2 or later. Alternatively, if you are directly using werkzeug/gunicorn, you should change your setup to use a reverse proxy such as NGINX, as sites behind a reverse proxy are not affected.