{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4799 exists.","fix":"No fix has been published for CVE-2005-4799 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4799 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 May 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-4799 and fix it if it is affected.\n\nWhat it is: CVE-2005-4799 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 May 2006. Any signed-in user can exploit it 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-2005-4799 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-2005-4799/ (Markdown: https://insights.sbomify.com/CVE-2005-4799/index.md)","id":"CVE-2005-4799","markdown":"https://insights.sbomify.com/CVE-2005-4799/index.md","name":"CVE-2005-4799","record":{"aliases":["GHSA-8mq7-xqr4-2h23"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP image gallery","requires_auth":"low_privilege","summary":"Remote attackers can inject arbitrary web script or HTML via image comment fields or view parameters in YaPIG, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yapig","vendor":"yapig"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Multiple cross-site scripting (XSS) vulnerabilities in Yet Another PHP Image Gallery (YaPIG) 0.95b and earlier allow remote attackers to inject arbitrary web script or HTML via (1) the Homepage field (aka the Website field) in an \"image-related comment\" and (2) the img_size field in view.php.  NOTE: due to lack of details from the researcher, it is not clear whether the comment vector overlaps CVE-2005-1886.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-10-13","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-10-13","kind":"exploitdb","ref":"26345","stars":null,"title":"YaPiG 0.95b - 'view.php?img_size' Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2005-4799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2005"},"n_packages":0,"n_references":9,"next":{"headline":"Code injection in n/a","id":"CVE-2005-4800"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2005-4798"},"products":["n/a"],"published":"2006-05-15","related":[{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2005-4800","kev_date_added":null,"published":"2006-05-15"},{"cvss_score":7.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2005-4801","kev_date_added":null,"published":"2006-05-15"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2005-1881","kev_date_added":null,"published":"2005-06-07"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2005-1882","kev_date_added":null,"published":"2005-06-07"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2007-4951","kev_date_added":null,"published":"2007-09-18"},{"cvss_score":6.4,"headline":"Path traversal in n/a","id":"CVE-2005-1884","kev_date_added":null,"published":"2005-06-07"}],"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-08","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via image comment fields or view parameters in YaPIG, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2005-4799/"}