Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1amended

Angular (deprecated package) Cross-site Scripting

CVE-2022-25869GHSA-prc3-vjfx-vhm9

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm angular

    Affected
    <= 1.8.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2022-25869: 7.68% estimated exploitation activity in the next 30 days; percentile 94.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

All versions of package angular are vulnerable to Cross-site Scripting (XSS) due to insecure page caching in the Internet Explorer browser, which allows interpolation of <textarea elements. NPM package angular is deprecated. Those who want to receive security updates should use the actively maintained package @angular/core.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-prc3-vjfx-vhm9

  2. Revision 1 · created ·

    Published from osv record GHSA-prc3-vjfx-vhm9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-25869

Advisory: Angular (deprecated package) Cross-site Scripting
IDs: CVE-2022-25869, GHSA-prc3-vjfx-vhm9
Record: https://patchnext.com/advisories/cve-2022-25869 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm angular: affected <= 1.8.3

## Suggested inspection (read-only)
- `npm ls angular --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on angular.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-prc3-vjfx-vhm9 (OSV record GHSA-prc3-vjfx-vhm9 lists affected ranges: npm angular >=0 <=1.8.3)
- Verified: https://github.com/advisories/GHSA-prc3-vjfx-vhm9 (GitHub-reviewed advisory GHSA-prc3-vjfx-vhm9 lists affected ranges: npm angular >=0 <=1.8.3)

Commands are suggestions: review each one before running it.

Loading voting…