{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0195 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2006-0195 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 24 Feb 2006. 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-2006-0195 and fix it if it is affected.\n\nWhat it is: CVE-2006-0195 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 24 Feb 2006. 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-2006-0195 in the wild and no public exploit code.\n\nAffected product: Squirrelmail Squirrelmail. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2006-0195/ (Markdown: https://insights.sbomify.com/CVE-2006-0195/index.md)","id":"CVE-2006-0195","markdown":"https://insights.sbomify.com/CVE-2006-0195/index.md","name":"CVE-2006-0195","record":{"aliases":["GHSA-pm99-m8ww-5fw3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SquirrelMail webmail","requires_auth":"none","summary":"Remote attackers can execute cross-site scripting attacks in SquirrelMail via crafted style sheet specifiers, requiring user interaction to trigger.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"squirrelmail","vendor":"squirrelmail"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Interpretation conflict in the MagicHTML filter in SquirrelMail 1.4.0 to 1.4.5 allows remote attackers to conduct cross-site scripting (XSS) attacks via style sheet specifiers with invalid (1) \"/*\" and \"*/\" comments, or (2) a newline in a \"url\" specifier, which is processed by certain web browsers including Internet Explorer.","ecosystems":[],"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":"Cross-site scripting in n/a","id":"CVE-2006-0195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"squirrelmail:squirrelmail","products":["squirrelmail:squirrelmail"],"type":"xss","year":"2006"},"n_packages":0,"n_references":20,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-0196"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0194"},"products":["n/a"],"published":"2006-02-24","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2002-0516","kev_date_added":null,"published":"2003-04-02"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2020-14932","kev_date_added":null,"published":"2020-06-20"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2020-14933","kev_date_added":null,"published":"2020-06-20"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-7692","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":7.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2007-2631","kev_date_added":null,"published":"2007-05-13"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2006-2842","kev_date_added":null,"published":"2006-06-06"},{"cvss_score":7.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2002-1648","kev_date_added":null,"published":"2005-03-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can execute cross-site scripting attacks in SquirrelMail via crafted style sheet specifiers, requiring user interaction to trigger.","url":"https://insights.sbomify.com/CVE-2006-0195/"}