CVE-2020-11031

What it is

In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library chosen is sodium.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-09-23 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:48 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-09-23 16:15 UTC

Last modified

2026-06-17 02:48 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-327 · Broken cryptographic algorithm

Record status

Modified

Affected

• glpi-project Glpi < 9.5.0

Attack profile CVSS 3.1 · 7.8

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-11031.md and follow it. Check whether this project is affected by CVE-2020-11031. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge