# CVE-2022-4642: tatoeba2 Profile Name cross site scripting

> Remote attackers can inject malicious scripts via profile names in Tatoeba2, potentially executing code in victim browsers.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Dec 2022
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-fvfc-c6j5-fh4r

## What is CVE-2022-4642?

CVE-2022-4642 is a low-severity cross-site scripting vulnerability in unspecified tatoeba2, published on 21 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in tatoeba2. It has been classified as problematic. This affects an unknown part of the component Profile Name Handler. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version prod_2022-10-30 is able to address this issue. The name of the patch is 91110777fc8ddf1b4a2cf4e66e67db69b9700361. It is recommended to upgrade the affected component. The identifier VDB-216501 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2022-4642?

It affects 1 product.


Products: Tatoeba Tatoeba2.

## How do I fix CVE-2022-4642?

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

## Is CVE-2022-4642 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4642 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4642 and fix it if it is affected.

What it is: CVE-2022-4642 is a low-severity cross-site scripting vulnerability in unspecified tatoeba2, published on 21 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4642 exists.

Affected product: unspecified tatoeba2. 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-2022-4642/ (Markdown: https://insights.sbomify.com/CVE-2022-4642/index.md)
```

## Sources

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

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