{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6119 exists.","fix":"No fix has been published for CVE-2008-6119 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-6119 is a high-severity code injection vulnerability in n/a, published on 11 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-6119 and fix it if it is affected.\n\nWhat it is: CVE-2008-6119 is a high-severity code injection vulnerability in n/a, published on 11 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6119 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-2008-6119/ (Markdown: https://insights.sbomify.com/CVE-2008-6119/index.md)","id":"CVE-2008-6119","markdown":"https://insights.sbomify.com/CVE-2008-6119/index.md","name":"CVE-2008-6119","record":{"aliases":["GHSA-q9rm-jjc4-w523"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Goople CMS","requires_auth":"high_privilege","summary":"Remote attackers with admin access can inject arbitrary PHP code into Goople CMS via username and password parameters, leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"goople_cms","vendor":"goople_cms"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Static code injection vulnerability in gooplecms/admin/account/action/editpass.php in Goople CMS 1.7 allows remote attackers to inject arbitrary PHP code into admin/userandpass.php via the (1) username and (2) password parameters.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2008-11-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2008-11-23","kind":"exploitdb","ref":"7205","stars":null,"title":"Goople CMS 1.7 - Insecure Cookie Handling"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2008-6119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2008"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2008-6120"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2008-6118"},"products":["n/a"],"published":"2009-02-11","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2008-6118","kev_date_added":null,"published":"2009-02-11"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2009-0121","kev_date_added":null,"published":"2009-01-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2009-0111","kev_date_added":null,"published":"2009-01-09"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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 with admin access can inject arbitrary PHP code into Goople CMS via username and password parameters, leading to code execution.","url":"https://insights.sbomify.com/CVE-2008-6119/"}