{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0350 exists.","fix":"No fix has been published for CVE-2006-0350 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0350 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jan 2006. It can be exploited over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-0350 and fix it if it is affected.\n\nWhat it is: CVE-2006-0350 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jan 2006. It can be exploited over the network, 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-0350 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-0350/ (Markdown: https://insights.sbomify.com/CVE-2006-0350/index.md)","id":"CVE-2006-0350","markdown":"https://insights.sbomify.com/CVE-2006-0350/index.md","name":"CVE-2006-0350","record":{"aliases":["GHSA-4pgg-mmwf-2c8w"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"EggBlog web application","requires_auth":"unknown","summary":"Remote attackers can inject arbitrary web script or HTML via the message field in EggBlog, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"eggblog","vendor":"epic_designs"}],"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 eggblog 2.0 allow remote attackers to inject arbitrary web script or HTML via the message field to topic.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-01-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-01-18","kind":"exploitdb","ref":"27111","stars":null,"title":"EggBlog 2.0 - 'message' Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2006-0350","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2006"},"n_packages":0,"n_references":7,"next":{"headline":"Denial of service in n/a","id":"CVE-2006-0351"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-0349"},"products":["n/a"],"published":"2006-01-21","related":[{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2005-4546","kev_date_added":null,"published":"2005-12-28"},{"cvss_score":7.5,"headline":"Business logic in n/a","id":"CVE-2006-2727","kev_date_added":null,"published":"2006-06-01"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-0349","kev_date_added":null,"published":"2006-01-21"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2006-6046","kev_date_added":null,"published":"2006-11-22"},{"cvss_score":6.4,"headline":"SQL injection in n/a","id":"CVE-2006-2725","kev_date_added":null,"published":"2006-06-01"},{"cvss_score":4.3,"headline":"SQL injection in n/a","id":"CVE-2005-4547","kev_date_added":null,"published":"2005-12-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)"},{"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 message field in EggBlog, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2006-0350/"}