Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-11035

weak CSRF tokens in GLPI

High7.5EPSS 0.90%
Published
Updated
Reserved
Assigned by
GitHub_M

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.

Scores

CVSS scores of CVE-2020-11035, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
NVDNVD · Modified3.1Critical9.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS (exploitation in 30 days)
0.90% · top 40% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Weakness

Affected products

References (3)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-11035 badge
[![CVE-2020-11035](https://trackcve.app/badge/CVE-2020-11035.svg)](https://trackcve.app/cve/CVE-2020-11035)

Record last updated .