# CVE-2021-32616: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in 1CDN

> An attacker can inject JavaScript into 1CDN file sharing software, allowing client-side code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **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:** 28 May 2021
- **Updated:** 3 Aug 2024

## What is CVE-2021-32616?

CVE-2021-32616 is a high-severity cross-site scripting vulnerability in onedotprojects cdn, published on 28 May 2021. 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

1CDN is open-source file sharing software. In 1CDN before commit f88a2730fa50fc2c2aeab09011f6f142fd90ec25, there is a basic cross-site scripting vulnerability that allows an attacker to inject /<script>//code</script> and execute JavaScript code on the client side.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-32616?

It affects 1 product.


Products: 1cdn Project 1cdn.

## How do I fix CVE-2021-32616?

No fix has been published for CVE-2021-32616 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-32616 being exploited?

There is no known exploitation of CVE-2021-32616 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32616 and fix it if it is affected.

What it is: CVE-2021-32616 is a high-severity cross-site scripting vulnerability in onedotprojects cdn, published on 28 May 2021. 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 CVE-2021-32616 in the wild and no public exploit code.

Affected product: onedotprojects cdn. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2021-32616/ (Markdown: https://insights.sbomify.com/CVE-2021-32616/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32616
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32616
- OSV: https://osv.dev/vulnerability/CVE-2021-32616

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-32616/
Summaries are generated and may contain mistakes; the official description above is the record.