{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-24801 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-24801 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24801 is a high-severity vulnerability in Glpi-Project Glpi, published on 18 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24801 and fix it if it is affected.\n\nWhat it is: CVE-2025-24801 is a high-severity vulnerability in Glpi-Project Glpi, published on 18 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-24801 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-24801/ (Markdown: https://insights.sbomify.com/CVE-2025-24801/index.md)","id":"CVE-2025-24801","markdown":"https://insights.sbomify.com/CVE-2025-24801/index.md","name":"CVE-2025-24801","record":{"aliases":["GHSA-g2p3-33ff-r555","UBUNTU-CVE-2025-24801"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"low_privilege","summary":"Authenticated attackers can upload and execute PHP files on the GLPI server, leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"glpi","vendor":"glpi-project"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"GLPI is a free asset and IT management software package. An authenticated user can upload and force the execution of *.php files located on the GLPI server. This vulnerability is fixed in 10.0.18.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-04-19","github_poc":4,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-05T23:22:18Z","kind":"github_poc","ref":"https://github.com/fatkz/CVE-2025-24801","stars":3,"title":"CVE-2025-24801 Exploit "},{"date":"2025-04-19T01:59:30Z","kind":"github_poc","ref":"https://github.com/r1beirin/Exploit-CVE-2025-24801","stars":1,"title":null},{"date":"2026-10-02T12:08:15Z","kind":"github_poc","ref":"https://github.com/kevenpanchal/CVE-2025-24801-GLPI-10.0.17-and-prior-Authenticated-RCE","stars":0,"title":null},{"date":"2026-10-14T15:40:47Z","kind":"github_poc","ref":"https://github.com/PeaMatNgu/cve-2025-24801-glpi","stars":0,"title":"Reproducible local lab and source analysis for CVE-2025-24801 in GLPI 10.0.16"}],"tier":"poc_unverified"},"has_fix":false,"headline":"GLPI allows authenticated remote code execution","id":"CVE-2025-24801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"glpi-project:glpi","products":["glpi-project:glpi"],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Soundness issue with Plonky2 look up tables","id":"CVE-2025-24802"},"packages":[],"prev":{"headline":"Critical vulnerability in `ismp-grandpa` \u003cv15.0.1","id":"CVE-2025-24800"},"products":["glpi"],"published":"2025-03-18","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["glpi-project"]},"summary":"Authenticated attackers can upload and execute PHP files on the GLPI server, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2025-24801/"}