{"answers":{"affected":"2 open source packages ship an affected version, including express-xss-sanitizer. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21169 exists.","fix":"Upgrade express-xss-sanitizer to 1.1.3 or later.","what":"CVE-2022-21169 is a high-severity vulnerability in express-xss-sanitizer, published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21169 and fix it if it is affected.\n\nWhat it is: CVE-2022-21169 is a high-severity vulnerability in express-xss-sanitizer, published on 26 Sep 2022. 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-2022-21169 exists.\n\nAffected packages and fixed versions:\n- express-xss-sanitizer (npm): affected all versions; fixed in 1.1.3\n- express-xss-sanitizer (npm): affected all versions; fixed in 1.1.3\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-2022-21169/ (Markdown: https://insights.sbomify.com/CVE-2022-21169/index.md)","id":"CVE-2022-21169","markdown":"https://insights.sbomify.com/CVE-2022-21169/index.md","name":"CVE-2022-21169","record":{"aliases":["GHSA-grjp-4jmr-mjcw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js XSS sanitizer","requires_auth":"none","summary":"Attackers can bypass XSS sanitization via prototype pollution in the express-xss-sanitizer library, potentially allowing malicious script execution.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"express_xss_sanitizer","vendor":"express_xss_sanitizer_project"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"The package express-xss-sanitizer before 1.1.3 are vulnerable to Prototype Pollution via the allowedTags attribute, allowing the attacker to bypass xss sanitization.","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":"Prototype Pollution","id":"CVE-2022-21169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Security feature bypass in i-FILTER, i-FILTER Browser \u0026 Cloud MultiAgent for Windows, and D-SPA using i-FILTER","id":"CVE-2022-21170"},"packages":[{"ecosystem":"npm","fixed":["1.1.3"],"introduced":["0"],"last_affected":[],"package":"express-xss-sanitizer","purl":null,"source":"GHSA-grjp-4jmr-mjcw"},{"ecosystem":"npm","fixed":["1.1.3"],"introduced":["0"],"last_affected":[],"package":"express-xss-sanitizer","purl":"pkg:npm/express-xss-sanitizer","source":"GHSA-grjp-4jmr-mjcw"}],"prev":{"headline":"ICSA-22-090-03 Fuji Electric Alpha5","id":"CVE-2022-21168"},"products":["express-xss-sanitizer"],"published":"2022-09-26","related":[{"cvss_score":8.2,"headline":"Express XSS Sanitizer: allowedTags/allowedAttributes bypass leads to permissive sanitization (XSS risk)","id":"CVE-2026-33979","kev_date_added":null,"published":"2026-03-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-05-21","vendors":["n/a"]},"summary":"Attackers can bypass XSS sanitization via prototype pollution in the express-xss-sanitizer library, potentially allowing malicious script execution.","url":"https://insights.sbomify.com/CVE-2022-21169/"}