Cross-Site Scripting in takeapeekGHSA-4q2f-8g74-qm56
GHSA-4q2f-8g74-qm56 is a security vulnerability in takeapeek. No vendor fix is recorded yet; mitigation options are listed below.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
takeapeeknpmDescription
All versions of takeapeek are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize filenames, allowing attackers to execute arbitrary JavaScript in the victim's browser through files with names containing malicious code.
Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | takeapeek | ≥ 0.0.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for takeapeek, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of takeapeek has shipped for GHSA-4q2f-8g74-qm56 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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
Is GHSA-4q2f-8g74-qm56 in your dependencies?
Find it across npm, including transitive dependencies.