Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65035: CWE-502: Deserialization of Untrusted Data in pluginsGLPI databaseinventory

0
Medium
VulnerabilityCVE-2025-65035cvecve-2025-65035cwe-502
Published: Fri Dec 19 2025 (12/19/2025, 16:35:56 UTC)
Source: CVE Database V5
Vendor/Project: pluginsGLPI
Product: databaseinventory

Description

CVE-2025-65035 is a medium severity vulnerability in the pluginsGLPI Database Inventory Plugin versions prior to 1. 1. 2. It involves unsafe deserialization of user-controlled data stored insecurely in the database, allowing arbitrary PHP object instantiation on every page load. Exploitation requires prior database write access through another vulnerability or misconfiguration, as well as high privileges and user interaction. The vulnerability can lead to full compromise of confidentiality, integrity, and availability of the affected system. Version 1. 1. 2 of the plugin addresses this issue. European organizations using vulnerable versions of pluginsGLPI databaseinventory should prioritize patching and review their access controls to prevent exploitation.

AI-Powered Analysis

AILast updated: 12/19/2025, 16:50:56 UTC

Technical Analysis

The vulnerability identified as CVE-2025-65035 affects the pluginsGLPI Database Inventory Plugin, specifically versions prior to 1.1.2. This plugin manages Teclib's inventory agents to perform database inventories on workstations. The core issue is an unsafe deserialization flaw (CWE-502) where user-controlled data, specifically via the 'computergroup' parameter, is stored insecurely in the database. This data is later unserialized on every page load without proper validation or sanitization, enabling an attacker to instantiate arbitrary PHP objects. Such arbitrary object instantiation can lead to remote code execution, privilege escalation, or other malicious actions depending on the objects available in the application context. However, exploitation requires that the attacker first obtains database write access, which typically necessitates exploiting another vulnerability or misconfiguration. Additionally, the CVSS vector indicates that exploitation requires network access (AV:N), high attack complexity (AC:H), privileges (PR:H), and user interaction (UI:R). The impact on confidentiality, integrity, and availability is high, as arbitrary code execution can compromise the entire system. The vulnerability was reserved in November 2025 and published in December 2025, with no known exploits in the wild at the time of reporting. The issue is fixed in version 1.1.2 of the plugin, which should be applied promptly.

Potential Impact

For European organizations, this vulnerability poses a significant risk if they use the pluginsGLPI Database Inventory Plugin in versions before 1.1.2. Successful exploitation can lead to full system compromise, including unauthorized data access, data manipulation, and service disruption. Given that GLPI is widely used for IT asset and service management, attackers could leverage this vulnerability to pivot within networks, escalate privileges, or disrupt critical IT operations. The requirement for prior database write access and user interaction somewhat limits the attack surface, but organizations with weak internal controls or exposed management interfaces remain at risk. The high impact on confidentiality, integrity, and availability means sensitive organizational data and operational continuity could be severely affected. This is particularly critical for sectors with strict data protection regulations such as GDPR in Europe, where data breaches can lead to heavy fines and reputational damage.

Mitigation Recommendations

European organizations should immediately upgrade the pluginsGLPI Database Inventory Plugin to version 1.1.2 or later to remediate this vulnerability. Beyond patching, organizations must audit and tighten database access controls to prevent unauthorized write access, as exploitation depends on this prerequisite. Implement strict input validation and sanitization for any user-supplied data stored in the database to reduce risks of unsafe deserialization. Employ web application firewalls (WAFs) with rules targeting deserialization attacks to detect and block suspicious payloads. Conduct thorough security assessments and penetration tests focusing on GLPI deployments to identify any other vulnerabilities or misconfigurations. Monitor logs for unusual activity related to the 'computergroup' parameter or PHP object instantiation patterns. Finally, educate administrators and users about the risks of interacting with untrusted data and the importance of applying security updates promptly.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-13T15:36:51.684Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69458084f063e4fadff5e842

Added to database: 12/19/2025, 4:42:44 PM

Last enriched: 12/19/2025, 4:50:56 PM

Last updated: 12/19/2025, 6:02:04 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats