# CVE-2021-46251: Cross-site scripting in n/a

> Attackers can execute arbitrary web scripts via a crafted POST request in the ScratchOAuth2 library, requiring a patch to mitigate.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:L/PR:N/S:C/UI:R`)
- **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:** 15 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qm66-q3cq-c2q3

## What is CVE-2021-46251?

CVE-2021-46251 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Feb 2022. 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

A reflected cross-site scripting (XSS) in ScratchOAuth2 before commit 1603f04e44ef67dde6ccffe866d2dca16defb293 allows attackers to execute arbitrary web scripts or HTML via a crafted POST request.

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

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

It affects 1 product.


Products: Scratchoauth2 Project Scratchoauth2.

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

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

## Is CVE-2021-46251 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-46250](https://insights.sbomify.com/CVE-2021-46250/): Auth bypass in n/a (critical 10.0)
- [CVE-2021-29437](https://insights.sbomify.com/CVE-2021-29437/): Account compromise by man-in-the-middle attack (high 8.0)
- [CVE-2021-46249](https://insights.sbomify.com/CVE-2021-46249/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-46251 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Feb 2022. 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-46251 in the wild and no public exploit code.

Affected product: n/a. 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-46251/ (Markdown: https://insights.sbomify.com/CVE-2021-46251/index.md)
```

## Sources

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

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