CVE-2020-25032

Description

An issue was discovered in Flask-CORS (aka CORS Middleware for Flask) before 3.0.9. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.

Severity
HIGH
CVSS v3
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N · source nvd
Exploit chance (EPSS)
3.909%
chance of exploitation in the next 30 days
higher than 90.5% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2020-08-31Published by the CNA03:57 UTC
  2. 2021-05-06GitHub advisory published (GHSA-xc3p-ff3m-f46v)248 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-xc3p-ff3m-f46v, affected packages:

PackageVulnerable versionsFixed in
PyPI flask-corsbefore 3.0.93.0.9

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
flask-cors_project flask-corsbefore 3.0.9fixed in 3.0.93.0.9
debian debian_linux10.0no fix listednot listed
opensuse backports_sle15.0no fix listednot listed
opensuse leap15.1no fix listed15.2no fix listednot listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources