How severe is CVE-2021-32670?

CVE-2021-32670 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-32670?

CVE-2021-32670 affects the following packages: datasette (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2021-32670?

Update datasette to 0.56.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32670 is resolved across your whole dependency graph.

How do I detect CVE-2021-32670 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-32670 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2021-32670 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-32670 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-32670?

CVE-2021-32670 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-32670?

CVE-2021-32670 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2021-32670 published, and has it been updated?

CVE-2021-32670 was published on June 7, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2021-32670 — datasette

MEDIUM

CVE-2021-32670 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in datasette. A fix is available for datasette — see the affected versions and patch details below.

Duplicate Advisory: Reflected cross-site scripting issue in Datasette

Also known asGHSA-gff3-739c-gxfq GHSA-xw7c-jx9m-xh5gPYSEC-2021-89

Published

Jun 7, 2021

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍datasette

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-xw7c-jx9m-xh5g. This link is maintained to preserve external references.

Original Description

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 vulnerability. This vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as 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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`datasette`	all versions	0.56.1`pip install --upgrade 'datasette==0.56.1'`

Affected Products

1 product · 1 configurations

Application

datasettedatasette

< 0.56.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datasette to 0.56.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32670 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-xw7c-jx9m-xh5g. This link is maintained to preserve external references. ## Original Description 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 plugin

O3 Security · Impact-Aware SCA

Is CVE-2021-32670 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

datasette

4.4/10

Code-Review2/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Jun 7, 2021

Last updated

Oct 20, 2026

Identifiers

CVE-2021-32670

GHSA-gff3-739c-gxfq

PYSEC-2021-89

References

Advisorydatasette.io · datasette auth passwords Advisorygithub.com · GHSA xw7c jx9m xh5g Advisoryowasp.org · xss Advisorypypi.org · datasette Advisorynvd.nist.gov · CVE 2021 32670 Fixgithub.com Webpypi.org · datasette

Related vulnerabilities

Also affects datasette

This CVE is medium severity; 2 of 3 other CVEs affecting datasette are rated as high or higher (top: moderate).

CVE-2025-64481CVE-2023-40570GHSA-q6j3-c4wc-63vw

Same weakness: CWE-79

This CVE is medium severity; 3 of 5 other CVEs with CWE-79 are rated as high or higher (top: high).

CVE-2026-126075CVE-2026-126063CVE-2026-110802CVE-2026-123364CVE-2026-118670Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026