{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0650 exists.","fix":"No fix has been published for CVE-2006-0650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0650 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 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-0650 and fix it if it is affected.\n\nWhat it is: CVE-2006-0650 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0650 exists.\n\nAffected product: n/a. 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-0650/ (Markdown: https://insights.sbomify.com/CVE-2006-0650/index.md)","id":"CVE-2006-0650","markdown":"https://insights.sbomify.com/CVE-2006-0650/index.md","name":"CVE-2006-0650","record":{"aliases":["GHSA-rw67-g7qx-mx6h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"CPAINT library","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script or HTML via the cpaint_response_type parameter in the CPAINT library, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cpaint","vendor":"cpaint"}],"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":"Cross-site scripting (XSS) vulnerability in cpaint2.inc.php in the CPAINT library before 2.0.3, as used in multiple scripts, allows remote attackers to inject arbitrary web script or HTML via the cpaint_response_type parameter, which is displayed in a resulting error message, as demonstrated using a hex-encoded IFRAME tag.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-02-08","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-02-08","kind":"exploitdb","ref":"27173","stars":null,"title":"CPAINT 1.3/2.0.2 - 'TYPE.php' Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2006-0650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2006"},"n_packages":0,"n_references":8,"next":{"headline":"SQL injection in n/a","id":"CVE-2006-0651"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-0649"},"products":["n/a"],"published":"2006-02-13","related":[{"cvss_score":7.5,"headline":"Command injection in n/a","id":"CVE-2005-2625","kev_date_added":null,"published":"2005-08-19"},{"cvss_score":6.4,"headline":"Unknown vulnerability in CPAINT Ajax Toolkit before 1.3-SP allows attackers to execute arbitrary PHP or ASP code or read files via unknown vectors.","id":"CVE-2005-2613","kev_date_added":null,"published":"2005-08-17"},{"cvss_score":5,"headline":"Code injection in n/a","id":"CVE-2005-2624","kev_date_added":null,"published":"2005-08-19"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via the cpaint_response_type parameter in the CPAINT library, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2006-0650/"}