{"answers":{"affected":"2 open source packages ship an affected version, including enshrined/svg-sanitize. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18857 in the wild and no public exploit code.","fix":"Upgrade enshrined/svg-sanitize to 0.12.0 or later.","what":"CVE-2019-18857 is a high-severity cross-site scripting vulnerability in n/a, published on 11 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18857 and fix it if it is affected.\n\nWhat it is: CVE-2019-18857 is a high-severity cross-site scripting vulnerability in n/a, published on 11 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-18857 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- enshrined/svg-sanitize (Packagist): affected all versions; fixed in 0.12.0\n- enshrined/svg-sanitize (Packagist): affected all versions; fixed in 0.12.0\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-2019-18857/ (Markdown: https://insights.sbomify.com/CVE-2019-18857/index.md)","id":"CVE-2019-18857","markdown":"https://insights.sbomify.com/CVE-2019-18857/index.md","name":"CVE-2019-18857","record":{"aliases":["GHSA-gf8j-v8x5-h9qp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP SVG sanitizer","requires_auth":"none","summary":"An attacker can execute arbitrary JavaScript via crafted SVG attributes due to improper sanitization of whitespace in script values.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"svg-sanitizer","vendor":"svg-sanitizer_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"darylldoyle svg-sanitizer before 0.12.0 mishandles script and data values in attributes, as demonstrated by unexpected whitespace such as in the javascript\u0026#9;:alert substring.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"XSS in enshrined/svg-sanitize due to mishandled script and data values in attributes","id":"CVE-2019-18857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-18858"},"packages":[{"ecosystem":"Packagist","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"enshrined/svg-sanitize","purl":null,"source":"GHSA-gf8j-v8x5-h9qp"},{"ecosystem":"Packagist","fixed":["0.12.0"],"introduced":["0"],"last_affected":[],"package":"enshrined/svg-sanitize","purl":"pkg:composer/enshrined/svg-sanitize","source":"GHSA-gf8j-v8x5-h9qp"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-18856"},"products":["n/a"],"published":"2019-11-11","related":[{"cvss_score":6.2,"headline":"Cross-site Scripting in svg-sanitizer","id":"CVE-2022-23638","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":6.1,"headline":"Sanitizer bypass in svg-sanitizer","id":"CVE-2019-10772","kev_date_added":null,"published":"2019-12-11"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can execute arbitrary JavaScript via crafted SVG attributes due to improper sanitization of whitespace in script values.","url":"https://insights.sbomify.com/CVE-2019-18857/"}