{"answers":{"affected":"2 open source packages ship an affected version, including topthink/framework. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-17566 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-17566 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17566 is a critical SQL injection vulnerability in n/a, published on 26 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-17566 and fix it if it is affected.\n\nWhat it is: CVE-2018-17566 is a critical SQL injection vulnerability in n/a, published on 26 Sep 2018. 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-2018-17566 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- topthink/framework (Packagist): affected all versions; no fix listed\n- topthink/framework (Packagist): affected all versions; no fix listed\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-2018-17566/ (Markdown: https://insights.sbomify.com/CVE-2018-17566/index.md)","id":"CVE-2018-17566","markdown":"https://insights.sbomify.com/CVE-2018-17566/index.md","name":"CVE-2018-17566","record":{"aliases":["GHSA-75fm-52mm-q5rm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP web framework","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the delete function's WHERE condition in ThinkPHP, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"thinkphp","vendor":"thinkphp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"In ThinkPHP 5.1.24, the inner function delete can be used for SQL injection when its WHERE condition's value can be controlled by a user's request.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"ThinkPHP SQL injection vulnerability","id":"CVE-2018-17566","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Jekyll allows attackers to access arbitrary files by specifying a symlink","id":"CVE-2018-17567"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"topthink/framework","purl":null,"source":"GHSA-75fm-52mm-q5rm"},{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"topthink/framework","purl":"pkg:composer/topthink/framework","source":"GHSA-75fm-52mm-q5rm"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-17565"},"products":["n/a"],"published":"2018-09-26","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-63888","kev_date_added":null,"published":"2025-11-20"},{"cvss_score":9.8,"headline":"ThinkPHP Path Traversal Vulnerability","id":"CVE-2025-50706","kev_date_added":null,"published":"2025-08-05"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-50707","kev_date_added":null,"published":"2025-08-05"},{"cvss_score":9.8,"headline":"ThinkPHP deserialization vulnerability","id":"CVE-2024-48112","kev_date_added":null,"published":"2024-10-30"},{"cvss_score":9.8,"headline":"ThinkPHP deserialization vulnerability","id":"CVE-2024-44902","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in thinkphp","id":"CVE-2022-45982","kev_date_added":null,"published":"2023-02-08"},{"cvss_score":9.8,"headline":"ThinkPHP Framework vulnerable to remote code execution","id":"CVE-2022-47945","kev_date_added":null,"published":"2022-12-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the delete function's WHERE condition in ThinkPHP, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2018-17566/"}