CVE-2020-11035

weak CSRF tokens in GLPI

CRITICAL
9.3
CVSS Score
Published: May 5, 2020 at 09:30 PM UTC
Updated: June 17, 2026 at 02:48 AM UTC
2 products affected across 2 vendorsFedoraGlpi

Using GLPI by glpi-project?

Get instant alerts when new vulnerabilities affect GLPI - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.3
Exploit prediction
EPSS 0.9%

Description

In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 9.4.60.83.3 ≤ v < 9.4.6
Affected range stops below 9.4.6, so it looks safe — our inference, not a vendor statement

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-327

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card