{"answers":{"affected":"2 open source packages ship an affected version, including materialize-css. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25349 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25349 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25349 is a medium-severity cross-site scripting vulnerability in materialize-css, published on 1 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-25349 and fix it if it is affected.\n\nWhat it is: CVE-2022-25349 is a medium-severity cross-site scripting vulnerability in materialize-css, published on 1 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-25349 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- materialize-css (npm): affected all versions up to 1.0.0; no fix listed\n- materialize-css (npm): affected all versions up to 1.0.0; 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-2022-25349/ (Markdown: https://insights.sbomify.com/CVE-2022-25349/index.md)","id":"CVE-2022-25349","markdown":"https://insights.sbomify.com/CVE-2022-25349/index.md","name":"CVE-2022-25349","record":{"aliases":["GHSA-7jvx-f994-rfw2"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript UI library","requires_auth":"none","summary":"Attackers can execute arbitrary scripts via the autocomplete component due to improper input escaping in the materialize-css library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"materialize","vendor":"materializecss"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"All versions of package materialize-css are vulnerable to Cross-site Scripting (XSS) due to improper escape of user input (such as \u0026lt;not-a-tag /\u0026gt;) that is being parsed as HTML/JavaScript, and inserted into the Document Object Model (DOM). This vulnerability can be exploited when the user-input is provided to the autocomplete component.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site Scripting (XSS)","id":"CVE-2022-25349","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2022"},"n_packages":2,"n_references":3,"next":{"headline":"Command Injection in puppet-facter","id":"CVE-2022-25350"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"materialize-css","purl":null,"source":"GHSA-7jvx-f994-rfw2"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"materialize-css","purl":"pkg:npm/materialize-css","source":"GHSA-7jvx-f994-rfw2"}],"prev":{"headline":"Other in AttacheCase","id":"CVE-2022-25348"},"products":["materialize-css"],"published":"2022-05-01","related":[{"cvss_score":6.1,"headline":"Materialize-css vulnerable to Cross-site Scripting in tooltip component","id":"CVE-2019-11002","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":6.1,"headline":"Materialize-css vulnerable to Cross-site Scripting in autocomplete component","id":"CVE-2019-11003","kev_date_added":null,"published":"2019-04-08"},{"cvss_score":6.1,"headline":"Materialize-css vulnerable to Improper Neutralization of Input During Web Page Generation","id":"CVE-2019-11004","kev_date_added":null,"published":"2019-04-08"}],"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-09-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts via the autocomplete component due to improper input escaping in the materialize-css library.","url":"https://insights.sbomify.com/CVE-2022-25349/"}