glpi: Incorrect Implementation of Authentication Algorithm
CVE-2025-23046 is a high-severity incorrect implementation of authentication algorithm vulnerability in glpi from GLPI Project, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected glpi versions: >= 9.5.0, < 10.0.18. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of glpi you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GLPI Project | glpi | >= 9.5.0, < 10.0.18 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.3 | Medium | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
GLPI is a free asset and IT management software package. Starting in version 9.5.0 and prior to version 10.0.18, if a "Mail servers" authentication provider is configured to use an Oauth connection provided by the OauthIMAP plugin, anyone can connect to GLPI using a user name on which an Oauth authorization has already been established. Version 10.0.18 contains a patch. As a workaround, one may disable any "Mail servers" authentication provider configured to use an Oauth connection provided by the OauthIMAP plugin.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Implementation of Authentication Algorithm
The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.
More Incorrect Implementation of Authentication Algorithm vulnerabilities (CWE-303)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/glpi-project/glpi/security/advisories/GHSA-vfxc-qg3v-j2r5Third Party Advisory
Patches and release notes
- github.com/glpi-project/glpi/releases/tag/10.0.18Release Notes
Other vulnerabilities in glpi
- 7.1 High severity
- 9.2 Critical severity
- 8.7 High severity
- 7.2 High severity
- 8.5 High severity
- 7.1 High severity
Recent Incorrect Implementation of Authentication Algorithm vulnerabilities
- 9.8 Critical severity
- 9.6 Critical severity
- 8.8 High severity
- 9.3 Critical severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.