Search for packages
| purl | pkg:pypi/datasette@0.46 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-gj9p-gkjg-1khj
Aliases: CVE-2025-64481 GHSA-w832-gg5g-x44m PYSEC-2025-73 |
Datasette is an open source multi-tool for exploring and publishing data. In versions 0.65.1 and below and 1.0a0 through 1.0a19, deployed instances of Datasette include an open redirect vulnerability. Hits to the path //example.com/foo/bar/ (the trailing slash is required) will redirect the user to https://example.com/foo/bar. This problem has been patched in both Datasette 0.65.2 and 1.0a21. To workaround this issue, if Datasette is running behind a proxy, that proxy could be configured to replace // with / in incoming request URLs. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-hmeq-aurn-9yf9
Aliases: CVE-2021-32670 GHSA-gff3-739c-gxfq GHSA-xw7c-jx9m-xh5g PYSEC-2021-89 |
Datasette is an open source multi-tool for exploring and publishing data. The `?_trace=1` debugging feature in Datasette does not correctly escape generated HTML, resulting in a [reflected cross-site scripting](https://owasp.org/www-community/attacks/xss/#reflected-xss-attacks) vulnerability. This vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as [datasette-auth-passwords](https://datasette.io/plugins/datasette-auth-passwords) as an attacker could use the vulnerability to access protected data. Datasette 0.57 and 0.56.1 both include patches for this issue. If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters. |
Affected by 1 other vulnerability. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-wxgg-vdd2-9uc6 | CSRF tokens leaked in URL by canned query form |
GHSA-q6j3-c4wc-63vw
GMS-2020-699 |