CVE-2023-53943VulnerabilityPublished 18 Dec 2025

CVE-2023-53943: GLPI · Observable Discrepancy

Affects GLPISource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Glpi-Project GLPI	Affected =9.5.7	Fixed in–

AI-suggested

To mitigate CVE-2023-53943, organizations should first monitor vendor communications for official patches or updates addressing this vulnerability and apply them promptly once available. In the interim, implementing rate limiting or throttling on the password reset endpoint can reduce the feasibility of automated enumeration attacks. Customizing or standardizing password reset responses to avoid disclosing whether an email address is valid can also mitigate information leakage. Logging and monitoring password reset requests for unusual patterns or volumes can help detect enumeration attempts early. Organizations should educate users about phishing risks and encourage strong, unique passwords combined with multi-factor authentication (MFA) to reduce the impact of potential credential compromise. Network-level protections such as web application firewalls (WAFs) can be configured to detect and block suspicious password reset request patterns. Finally, reviewing and minimizing the exposure of GLPI instances to the public internet, restricting access to trusted networks, and enforcing strict access controls will further reduce attack surface.

Description

CVE-2023-53943 is a username enumeration vulnerability in GLPI version 9.5.7's lost password recovery mechanism. Attackers can submit password reset requests with different email addresses and observe response discrepancies to confirm valid user accounts. This vulnerability does not require authentication or user interaction and can be exploited remotely over the network. The CVSS 4.0 score is 6.9 (medium severity), reflecting the ease of exploitation and limited impact on confidentiality, integrity, and availability. While it does not directly allow account takeover, enumerating valid users can facilitate targeted phishing, social engineering, or brute force attacks. European organizations using GLPI 9.

Impact

For European organizations, the primary impact of CVE-2023-53943 is the exposure of valid user email addresses through the password reset mechanism. This information leakage can enable attackers to craft targeted phishing campaigns or launch brute force attacks against confirmed accounts, increasing the risk of credential compromise. In sectors where GLPI is used to manage sensitive IT infrastructure, such as government agencies, healthcare, and critical infrastructure providers, this vulnerability could indirectly lead to more severe breaches if attackers leverage enumerated usernames for lateral movement or privilege escalation. While the vulnerability itself does not allow direct account takeover or data manipulation, it lowers the barrier for attackers to identify valuable targets within an organization. The medium severity rating reflects that the confidentiality of user identity information is impacted, but integrity and availability remain unaffected. European organizations with large user bases or those that integrate GLPI with other identity or access management systems may face higher risks due to the potential for chained attacks. Additionally, compliance with data protection regulations such as GDPR may be impacted if user data is exposed or leveraged in subsequent attacks.

References

Community reviews

Loading reviews…