CSRF tokens leaked in URL by canned query form

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The HTML form for a read-only canned query includes the hidden CSRF token field added in #798 for writable canned queries (#698). This means that submitting those read-only forms exposes the CSRF token in the URL - for example on https://latest.datasette.io/fixtures/neighborhoodsearch submitting the form took me to: https://latest.datasette.io/fixtures/neighborhoodsearch?text=down&csrftoken=CSRFTOKEN-HERE This token could potentially leak to an attacker if the resulting page has a link to an external site on it and the user clicks the link, since the token would be exposed in the referral logs. Patches A fix for this issue has been released in Datasette 0.46. Workarounds You can fix this issue in a Datasette instance without upgrading by copying the 0.46 query.html template into a custom templates/ directory and running Datasette with the --template-dir=templates/ option. References Issue 918 discusses this in details: https://github.com/simonw/datasette/issues/918 For more…

Published by the source

11 Aug 2020, 14:54 UTC

Last modified by the source

2 Dec 2024, 05:44 UTC

Source last checked

26 Oct 2026, 13:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q6j3-c4wc-63vw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q6j3-c4wc-63vw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-q6j3-c4wc-63vw

Advisory: CSRF tokens leaked in URL by canned query form
IDs: GHSA-q6j3-c4wc-63vw
Record: https://patchnext.com/advisories/ghsa-q6j3-c4wc-63vw (revision 2, source checked 26 Oct 2026, 13:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: datasette 0.46. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI datasette: affected < 0.46; fixed in 0.46

## Suggested inspection (read-only)
- `python -m pip show datasette`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on datasette.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q6j3-c4wc-63vw (OSV record GHSA-q6j3-c4wc-63vw lists affected ranges: PyPI datasette >=0 <0.46 (fixed))
- Verified: https://github.com/advisories/GHSA-q6j3-c4wc-63vw (GitHub-reviewed advisory GHSA-q6j3-c4wc-63vw lists affected ranges: PyPI datasette >=0 <0.46)

Commands are suggestions: review each one before running it.