# CVE-2022-25869: Angular (deprecated package) Cross-site Scripting

> Cross-site scripting vulnerability in AngularJS allows attackers to execute scripts via insecure page caching in Internet Explorer.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P`)
- **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:** 15 Jul 2022
- **Updated:** 28 Jul 2025
- **Also known as:** DEBIAN-CVE-2022-25869, GHSA-prc3-vjfx-vhm9, MINI-wvhc-jwq9-f67p, UBUNTU-CVE-2022-25869

## What is CVE-2022-25869?

CVE-2022-25869 is a medium-severity cross-site scripting vulnerability in AngularJS.Core, published on 15 Jul 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

All versions of the package angular; all versions of the package angularjs.core; all versions of the package angularjs are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of <textarea> elements.

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

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

2 open source packages ship an affected version, including angular. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `angular` | npm | All versions to 1.8.3 | None |
| `angular` | npm | All versions to 1.8.3 | None |

Products: Angularjs Angularjs.

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

No fix published yet.

## Is CVE-2022-25869 being exploited?

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

Public exploit code:

- A minimal reproduction of an AngularJS <textarea> XSS vulnerability on IE (tracked as CVE-2022-25869). (github_poc): https://github.com/neverendingsupport/angularjs-poc-cve-2022-25869

## Other vulnerabilities in AngularJS.Core

- [CVE-2019-10768](https://insights.sbomify.com/CVE-2019-10768/): angular Prototype Pollution vulnerability (high 7.5)
- [CVE-2019-14863](https://insights.sbomify.com/CVE-2019-14863/): AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes (high 7.1)
- [CVE-2020-7676](https://insights.sbomify.com/CVE-2020-7676/): Angular vulnerable to Cross-site Scripting (medium 5.4)
- [CVE-2023-26116](https://insights.sbomify.com/CVE-2023-26116/): angular vulnerable to regular expression denial of service via the angular.copy() utility (medium 5.3)
- [CVE-2023-26117](https://insights.sbomify.com/CVE-2023-26117/): angular vulnerable to regular expression denial of service via the $resource service (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25869 is a medium-severity cross-site scripting vulnerability in AngularJS.Core, published on 15 Jul 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-2022-25869 in the wild and no public exploit code.

Affected packages and fixed versions:
- angular (npm): affected all versions up to 1.8.3; no fix listed
- angular (npm): affected all versions up to 1.8.3; 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/CVE-2022-25869/ (Markdown: https://insights.sbomify.com/CVE-2022-25869/index.md)
```

## Sources

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

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