# CVE-2024-33665: Cross-site scripting in n/a

> Cross-site scripting vulnerability in angular-translate allows attackers to execute arbitrary scripts via crafted translation keys.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** Yes
- **Published:** 26 Apr 2024
- **Updated:** 29 Oct 2024
- **Also known as:** CLSA-2026-1775694704, CLSA-2026-1775694705, GHSA-jrv8-4h2c-vxmj

## What is CVE-2024-33665?

CVE-2024-33665 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2024. 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

angular-translate through 2.19.1 allows XSS via a crafted key that is used by the translate directive. NOTE: the vendor indicates that there is no documentation indicating that a key is supposed to be safe against XSS attacks.

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

## Which versions are affected by CVE-2024-33665?


## How do I fix CVE-2024-33665?

No fix published yet.

## Is CVE-2024-33665 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33665 and fix it if it is affected.

What it is: CVE-2024-33665 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2024. 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-2024-33665 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-2024-33665/ (Markdown: https://insights.sbomify.com/CVE-2024-33665/index.md)
```

## Sources

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

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