{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-66417 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66417 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66417 and fix it if it is affected.\n\nWhat it is: CVE-2025-66417 is a high-severity SQL injection vulnerability in Glpi-Project Glpi, published on 15 Jan 2026. 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-2025-66417 in the wild and no public exploit code.\n\nAffected product: Glpi-Project Glpi. 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-2025-66417/ (Markdown: https://insights.sbomify.com/CVE-2025-66417/index.md)","id":"CVE-2025-66417","markdown":"https://insights.sbomify.com/CVE-2025-66417/index.md","name":"CVE-2025-66417","record":{"aliases":["GHSA-p467-682w-9cc9","UBUNTU-CVE-2025-66417"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"none","summary":"Unauthenticated attackers can execute SQL injection via the inventory endpoint in GLPI, allowing unauthorized data access or modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"glpi","vendor":"glpi-project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"GLPI is a free asset and IT management software package. From 11.0.0, \u003c 11.0.3, an unauthenticated user can perform a SQL injection through the inventory endpoint. This vulnerability is fixed in 11.0.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-12-11","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-12-11T09:19:32Z","kind":"github_poc","ref":"https://github.com/lem0naids/CVE-2025-66417-POC","stars":4,"title":"POC SQLi CVE-2025-66417"}],"tier":"poc_unverified"},"has_fix":false,"headline":"GLPI has an unauthenticated SQL injection through the inventory endpoint","id":"CVE-2025-66417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"glpi-project:glpi","products":["glpi-project:glpi"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"urllib3 allows an unbounded number of links in the decompression chain","id":"CVE-2025-66418"},"packages":[],"prev":{"headline":"DNS Rebinding Protection Disabled by Default in Model Context Protocol Python SDK for Servers Running on Localhost","id":"CVE-2025-66416"},"products":["glpi"],"published":"2026-01-15","related":[{"cvss_score":9.8,"headline":"Teclib GLPI Remote Code Execution","id":"CVE-2022-35914","kev_date_added":"2023-03-07","published":"2022-09-19"},{"cvss_score":10,"headline":"GLPI vulnerable to unallowed PHP script execution","id":"CVE-2023-42802","kev_date_added":null,"published":"2023-11-02"},{"cvss_score":10,"headline":"GLPI vulnerable to SQL injection and Stored XSS via inventory agent request","id":"CVE-2023-28849","kev_date_added":null,"published":"2023-04-05"},{"cvss_score":10,"headline":"SQL injection in GLPI","id":"CVE-2022-35947","kev_date_added":null,"published":"2022-09-14"},{"cvss_score":9.8,"headline":"SQL injection with _actor parameter in GLPI","id":"CVE-2022-31056","kev_date_added":null,"published":"2022-06-28"},{"cvss_score":9.8,"headline":"SQL injection on login page in GLPI","id":"CVE-2022-31061","kev_date_added":null,"published":"2022-06-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-44617","kev_date_added":null,"published":"2022-03-28"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-15","vendors":["glpi-project"]},"summary":"Unauthenticated attackers can execute SQL injection via the inventory endpoint in GLPI, allowing unauthorized data access or modification.","url":"https://insights.sbomify.com/CVE-2025-66417/"}