pyspector
Affected
- introduced
0, fixed0.1.7(ecosystem)
Fixed versions
0.1.7
Fix
- Fixed version
0.1.7pip install --upgrade pyspector==0.1.7
Advisory
Also known as: CVE-2026-33140, GHSA-2gmv-2r3v-jxj2
Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution
Summary
PySpector versions <= 0.1.6 are affected by a stored Cross-Site Scripting (XSS) vulnerability in the HTML report generator. When PySpector scans a Python file containing JavaScript payloads (i.e. inside a string passed to eval() ), the flagged code snippet is interpolated into the HTML report without sanitization. Opening the generated report in a browser causes the embedded JavaScript to execute in the browser's local file context.
Impact
An attacker can craft a malicious Python file (for example, hosted in a public repository), designed to be scanned by PySpector. When a victim scans this file and opens the resulting HTML report, arbitrary JavaScript executes in their browser. While the file:// context limits the attacker's ability to exfiltrate cookies or make credentialed requests, the following is still achievable:
fetch() or XMLHttpRequest to file:// paths (browser-dependent)Any user of PySpector who scans untrusted code and generates HTML reports, is potentially affected.
PoC
The following steps reproduce the vulnerability on PySpector <= 0.1.6:
eval(), and run PySpector against the file, generating an HTML report:<img width="871" height="752" alt="image" src="https://github.com/user-attachments/assets/1b0a57f2-3632-4347-a9b7-6a94dc2e82b2" />
<img width="1920" height="920" alt="image" src="https://github.com/user-attachments/assets/a4075c4a-6153-41b4-ad77-81d009d7a9f8" />
Not rated by the source.
0, fixed 0.1.7 (ecosystem)0.1.7
0.1.7pip install --upgrade pyspector==0.1.7Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0