{"answers":{"affected":"2 open source packages ship an affected version, including angular.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0716 exists.","fix":"Product is end of life, replace it.","what":"CVE-2025-0716 is a medium-severity cross-site scripting vulnerability in Google AngularJS, published on 29 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0716 and fix it if it is affected.\n\nWhat it is: CVE-2025-0716 is a medium-severity cross-site scripting vulnerability in Google AngularJS, published on 29 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0716 exists.\n\nAffected packages and fixed versions:\n- angular (npm): affected all versions up to 1.8.3; no fix listed\n- angular (npm): affected all versions up to 1.8.3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-0716/ (Markdown: https://insights.sbomify.com/CVE-2025-0716/index.md)","id":"CVE-2025-0716","markdown":"https://insights.sbomify.com/CVE-2025-0716/index.md","name":"CVE-2025-0716","record":{"aliases":["DEBIAN-CVE-2025-0716","GHSA-j58c-ww9w-pwp5","MINI-8m45-cr8r-v3r5","MINI-wrf2-6vr4-9f42","ROOT-APP-NPM-CVE-2025-0716","UBUNTU-CVE-2025-0716"],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["security_bypass","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"AngularJS library","requires_auth":"none","summary":"Attackers can bypass image source restrictions in AngularJS SVG elements, enabling content spoofing and potential denial of service via large images.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HeroDevs","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-791","name":"Incomplete Filtering of Special Elements"}],"description":"Improper sanitization of the value of the 'href' and 'xlink:href' attributes in '\u003cimage\u003e' SVG elements in AngularJS allows attackers to bypass common image source restrictions. This can lead to a form of  Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing  and also negatively affect the application's performance and behavior by using too large or slow-to-load images.\n\nThis issue affects all versions of AngularJS.\n\nNote:\nThe AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see  here https://docs.angularjs.org/misc/version-support-status .","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AngularJS improper sanitization in SVG '\u003cimage\u003e' element","id":"CVE-2025-0716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Social Slider Feed \u003c 2.2.9 - Admin+ Stored XSS","id":"CVE-2025-0717"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.8.3"],"package":"angular","purl":null,"source":"GHSA-j58c-ww9w-pwp5"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.8.3"],"package":"angular","purl":"pkg:npm/angular","source":"GHSA-j58c-ww9w-pwp5"}],"prev":{"headline":"Insecure storage of sensitive information in MobaXTerm \u003c25.0.","id":"CVE-2025-0714"},"products":["AngularJS"],"published":"2025-04-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["Google"]},"summary":"Attackers can bypass image source restrictions in AngularJS SVG elements, enabling content spoofing and potential denial of service via large images.","url":"https://insights.sbomify.com/CVE-2025-0716/"}