Quick answers
- Is CVE-2025-0716 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-0716 being exploited in the wild.
- How severe is CVE-2025-0716?
- Low severity, with a CVSS score of 3.1, published 29 April 2025.
- Which products and versions are affected?
- angular (npm) SEMVER:introduced=0,last_affected=1.8.3.
- Is there a fix for CVE-2025-0716?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-0716 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-0716?
- Check whether you run angular (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability stems from improper sanitization of the 'href' and 'xlink:href' attributes in SVG <image> elements within AngularJS. An attacker can craft malicious SVG elements to bypass common image source validation controls and inject arbitrary image sources. This is a CWE-791 (Incorrect Filtering of Special Elements or Attributes) issue. The attack vector is network-based and requires no authentication or user interaction beyond viewing a page containing the malicious SVG. Exploitation can result in content spoofing attacks or performance degradation. Since AngularJS is end-of-life, no patch will be released.
Affected products
- Google AngularJS all versions up to and including 1.8.3
Identifiers
- CVE-2025-0716
- GHSA-j58c-ww9w-pwp5
Timeline
- 2025-04-29: disclosed
- 2025-04-30: advisory