{"id":"CVE-2026-33140","aliases":["GHSA-2gmv-2r3v-jxj2","PYSEC-2026-3029"],"title":"Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution","summary":"Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution","severity":"medium","vendor":"pyspector","product":"pyspector","ecosystem":"pip","affected":["pyspector < 0.1.7"],"patched":["pyspector 0.1.7"],"published":"2026-03-18","updated":"2026-07-13","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-2gmv-2r3v-jxj2","references":[{"url":"https://github.com/ParzivalHack/PySpector/security/advisories/GHSA-2gmv-2r3v-jxj2"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-33140"},{"url":"https://github.com/ParzivalHack/PySpector"}],"tags":["osv","pip"],"epss":0.00217,"epssPercentile":0.12406,"ingestedAt":"2026-07-13T18:57:51.305Z","slug":"CVE-2026-33140","body":"## Overview\n\n### Summary\nPySpector 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.\n\n### Impact\nAn 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:\n- Arbitrary DOM manipulation\n- Redirects to attacker-controlled pages\n- Theft of locally accessible data via `fetch()` or `XMLHttpRequest` to `file://` paths (browser-dependent)\n\nAny user of PySpector who scans untrusted code and generates HTML reports, is potentially affected.\n\n### PoC\n\nThe following steps reproduce the vulnerability on PySpector `<= 0.1.6`:\n1. Create a malicious Python file containing a JavaScript payload embedded in a string argument to `eval()`, and run PySpector against the file, generating an HTML report:\n<img width=\"871\" height=\"752\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1b0a57f2-3632-4347-a9b7-6a94dc2e82b2\" />\n2. Open the generated HTML report in any browser:\n<img width=\"1920\" height=\"920\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a4075c4a-6153-41b4-ad77-81d009d7a9f8\" />\n\n## Affected packages\n\n- `pyspector < 0.1.7`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `pyspector 0.1.7`","depth":"sunlit","depthScore":28,"depthScoreParts":{"impact":27.5,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}