XSS via JQLite DOM manipulation functions in AngularJS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary XSS may be triggered in AngularJS applications that sanitize user-controlled HTML snippets before passing them to JQLite methods like JQLite.prepend, JQLite.after, JQLite.append, JQLite.replaceWith, JQLite.append, new JQLite and angular.element. Description JQLite (DOM manipulation library that's part of AngularJS) manipulates input HTML before inserting it to the DOM in jqLiteBuildFragment. One of the modifications performed expands an XHTML self-closing tag. If jqLiteBuildFragment is called (e.g. via new JQLite(aString)) with user-controlled HTML string that was sanitized (e.g. with DOMPurify), the transformation done by JQLite may modify some forms of an inert, sanitized payload into a payload containing JavaScript - and trigger an XSS when the payload is inserted into DOM. This is similar to a bug in jQuery htmlPrefilter function that was fixed in 3.5.0. Proof of concept Note that the style element is not closed and <img would be a text node inside the style if inserted…

Published by the source

5 Aug 2020, 21:47 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5cp4-xmrw-59wf

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5cp4-xmrw-59wf

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

# Patch Next advisory brief: GHSA-5cp4-xmrw-59wf

Advisory: XSS via JQLite DOM manipulation functions in AngularJS
IDs: GHSA-5cp4-xmrw-59wf
Record: https://patchnext.com/advisories/ghsa-5cp4-xmrw-59wf (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: angular 1.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm angular: affected < 1.8.0; fixed in 1.8.0

## 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
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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-5cp4-xmrw-59wf (OSV record GHSA-5cp4-xmrw-59wf lists affected ranges: npm angular >=0 <1.8.0 (fixed))
- Verified: https://github.com/advisories/GHSA-5cp4-xmrw-59wf (GitHub-reviewed advisory GHSA-5cp4-xmrw-59wf lists affected ranges: npm angular >=0 <1.8.0)

Commands are suggestions: review each one before running it.