# CVE-2020-26212: Any GLPI CalDAV calendars is read-only for every authenticated user

> Any authenticated user can read other users' personal and group calendars via CalDAV, exposing sensitive scheduling data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qmw3-87hr-5wgx

## What is CVE-2020-26212?

CVE-2020-26212 is a high-severity missing authorization vulnerability in Glpi-Project Glpi, published on 25 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GLPI stands for Gestionnaire Libre de Parc Informatique and it is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. In GLPI before version 9.5.3, any authenticated user has read-only permissions to the planning of every other user, even admin ones. Steps to reproduce the behavior: 1. Create a new planning with 'eduardo.mozart' user (from 'IT' group that belongs to 'Super-admin') into it's personal planning at 'Assistance' > 'Planning'. 2. Copy the CalDAV url and use a CalDAV client (e.g. Thunderbird) to sync the planning with the provided URL. 3. Inform the username and password from any valid user (e.g. 'camila' from 'Proativa' group). 4. 'Camila' has read-only access to 'eduardo.mozart' personal planning. The same behavior happens to any group. E.g. 'Camila' has access to 'IT' group planning, even if she doesn't belong to this group and has a 'Self-service' profile permission). This issue is fixed in version 9.5.3. As a workaround, one can remove the `caldav.php` file to block access to CalDAV server.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-26212?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2020-26212?

No fix has been published for CVE-2020-26212 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-26212 being exploited?

There is no known exploitation of CVE-2020-26212 in the wild and no public exploit code.

## Other vulnerabilities in Glpi-Project Glpi

- [CVE-2022-35914](https://insights.sbomify.com/CVE-2022-35914/): Teclib GLPI Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-42802](https://insights.sbomify.com/CVE-2023-42802/): GLPI vulnerable to unallowed PHP script execution (critical 10.0)
- [CVE-2023-28849](https://insights.sbomify.com/CVE-2023-28849/): GLPI vulnerable to SQL injection and Stored XSS via inventory agent request (critical 10.0)
- [CVE-2022-35947](https://insights.sbomify.com/CVE-2022-35947/): SQL injection in GLPI (critical 10.0)
- [CVE-2022-31056](https://insights.sbomify.com/CVE-2022-31056/): SQL injection with _actor parameter in GLPI (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26212 and fix it if it is affected.

What it is: CVE-2020-26212 is a high-severity missing authorization vulnerability in Glpi-Project Glpi, published on 25 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26212 in the wild and no public exploit code.

Affected product: Glpi-Project Glpi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26212/ (Markdown: https://insights.sbomify.com/CVE-2020-26212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26212
- OSV: https://osv.dev/vulnerability/CVE-2020-26212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26212/
Summaries are generated and may contain mistakes; the official description above is the record.