# GHSA-4q2f-8g74-qm56: Cross-Site Scripting in takeapeek

> Attackers can execute arbitrary JavaScript in victims' browsers via malicious filenames, affecting users of the takeapeek npm package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-4q2f-8g74-qm56?

GHSA-4q2f-8g74-qm56 is a cross-site scripting vulnerability in takeapeek, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by GHSA-4q2f-8g74-qm56?

2 open source packages ship an affected version, including takeapeek.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `takeapeek` | npm | From 0.0.0 | None |
| `takeapeek` | npm | From 0.0.0 | None |

## How do I fix GHSA-4q2f-8g74-qm56?

No fix has been published for GHSA-4q2f-8g74-qm56 yet. Limit exposure of the affected software until one is available.

## Is GHSA-4q2f-8g74-qm56 being exploited?

There is no known exploitation of GHSA-4q2f-8g74-qm56 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4q2f-8g74-qm56 and fix it if it is affected.

What it is: GHSA-4q2f-8g74-qm56 is a cross-site scripting vulnerability in takeapeek, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-4q2f-8g74-qm56 in the wild and no public exploit code.

Affected packages and fixed versions:
- takeapeek (npm): affected from 0.0.0; no fix listed
- takeapeek (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4q2f-8g74-qm56/ (Markdown: https://insights.sbomify.com/GHSA-4q2f-8g74-qm56/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4q2f-8g74-qm56

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4q2f-8g74-qm56/
Summaries are generated and may contain mistakes; the official description above is the record.