{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4739 exists.","fix":"No fix has been published for CVE-2009-4739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-4739 is a medium-severity code injection vulnerability in n/a, published on 26 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-4739 and fix it if it is affected.\n\nWhat it is: CVE-2009-4739 is a medium-severity code injection vulnerability in n/a, published on 26 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4739 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-2009-4739/ (Markdown: https://insights.sbomify.com/CVE-2009-4739/index.md)","id":"CVE-2009-4739","markdown":"https://insights.sbomify.com/CVE-2009-4739/index.md","name":"CVE-2009-4739","record":{"aliases":["GHSA-2wc3-pmh3-j9cq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SkaDate Dating","requires_auth":"none","summary":"Remote attackers can execute arbitrary PHP code or local files via the language_id parameter in SkaDate Dating.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"skadate_online_dating_software","vendor":"skadate"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"PHP remote file inclusion vulnerability in index.php in SkaDate Dating allows remote attackers to execute arbitrary PHP code via a URL in the language_id parameter.  NOTE: this can also be leveraged to include and execute arbitrary local files via directory traversal sequences.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-07-27","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-07-27","kind":"exploitdb","ref":"9260","stars":null,"title":"skadate dating - Local File Inclusion / Remote File Inclusion / Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2009-4739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2009"},"n_packages":0,"n_references":6,"next":{"headline":"Path traversal in n/a","id":"CVE-2009-4740"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2009-4738"},"products":["n/a"],"published":"2010-03-26","related":[{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2009-4700","kev_date_added":null,"published":"2010-03-15"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2007-5299","kev_date_added":null,"published":"2007-10-09"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2009-4699","kev_date_added":null,"published":"2010-03-15"}],"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 can execute arbitrary PHP code or local files via the language_id parameter in SkaDate Dating.","url":"https://insights.sbomify.com/CVE-2009-4739/"}