{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-65035 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65035 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65035 is a medium-severity unsafe deserialization vulnerability in pluginsGLPI databaseinventory, published on 19 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-65035 and fix it if it is affected.\n\nWhat it is: CVE-2025-65035 is a medium-severity unsafe deserialization vulnerability in pluginsGLPI databaseinventory, published on 19 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-65035 in the wild and no public exploit code.\n\nAffected product: pluginsGLPI databaseinventory. 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-65035/ (Markdown: https://insights.sbomify.com/CVE-2025-65035/index.md)","id":"CVE-2025-65035","markdown":"https://insights.sbomify.com/CVE-2025-65035/index.md","name":"CVE-2025-65035","record":{"aliases":["GHSA-xc3r-32rx-3j4j"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"GLPI inventory plugin","requires_auth":"high_privilege","summary":"Attackers with database write access can trigger arbitrary PHP object instantiation via insecure deserialization in the GLPI Database Inventory Plugin.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"pluginsGLPI's Database Inventory Plugin \"manages\" the Teclib' inventory agents in order to perform an inventory of the databases present on the workstation. Prior to version 1.1.2, in certain conditions (database write access must first be obtained through another vulnerability or misconfiguration), user-controlled data is stored insecurely in the database via computergroup, and is later unserialized on every page load, allowing arbitrary PHP object instantiation. Version 1.1.2 fixes the issue.","ecosystems":[],"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":"GLPI Database Inventory Plugin Vulnerable to Stored Object Injection","id":"CVE-2025-65035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"XWiki Remote Macros vulnerable to remote code execution using the confluence details summary macro","id":"CVE-2025-65036"},"packages":[],"prev":{"headline":"Rallly Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId","id":"CVE-2025-65034"},"products":["databaseinventory"],"published":"2025-12-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-19","vendors":["pluginsGLPI"]},"summary":"Attackers with database write access can trigger arbitrary PHP object instantiation via insecure deserialization in the GLPI Database Inventory Plugin.","url":"https://insights.sbomify.com/CVE-2025-65035/"}