{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-2679 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-2679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-2679 is a high-severity SQL injection vulnerability in n/a, published on 23 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-2679 and fix it if it is affected.\n\nWhat it is: CVE-2015-2679 is a high-severity SQL injection vulnerability in n/a, published on 23 Mar 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-2679 in the wild and no public exploit code.\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-2015-2679/ (Markdown: https://insights.sbomify.com/CVE-2015-2679/index.md)","id":"CVE-2015-2679","markdown":"https://insights.sbomify.com/CVE-2015-2679/index.md","name":"CVE-2015-2679","record":{"aliases":["GHSA-m6vg-jvg4-5v4h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GeniXCMS","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands via vulnerable parameters in GeniXCMS, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"genixcms","vendor":"genixcms"}],"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-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Multiple SQL injection vulnerabilities in MetalGenix GeniXCMS before 0.0.2 allow remote attackers to execute arbitrary SQL commands via the (1) page parameter to index.php or (2) username parameter to gxadmin/login.php.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-03-10","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-03-10","kind":"exploitdb","ref":"36321","stars":null,"title":"GeniXCMS 0.0.1 - Multiple Vulnerabilities"}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2015-2679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2015"},"n_packages":0,"n_references":10,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2015-2680"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2015-2678"},"products":["n/a"],"published":"2015-03-23","related":[{"cvss_score":9.1,"headline":"GeniXCMS Arbitrary User Password Reset Vulnerability","id":"CVE-2017-8827","kev_date_added":null,"published":"2017-05-08"},{"cvss_score":8.8,"headline":"GeniXCMS arbitrary PHP code execution","id":"CVE-2017-14763","kev_date_added":null,"published":"2017-09-27"},{"cvss_score":8.8,"headline":"GeniXCMS arbitrary PHP code execution","id":"CVE-2017-14764","kev_date_added":null,"published":"2017-09-27"},{"cvss_score":8.8,"headline":"GeniXCMS SQL Injection","id":"CVE-2017-8377","kev_date_added":null,"published":"2017-05-01"},{"cvss_score":7.3,"headline":"GeniXCMS SQL injection vulnerability","id":"CVE-2016-10096","kev_date_added":null,"published":"2017-01-01"},{"cvss_score":7.2,"headline":"GeniXCMS SQL injection vulnerability","id":"CVE-2017-5346","kev_date_added":null,"published":"2017-01-12"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands via vulnerable parameters in GeniXCMS, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2015-2679/"}