# CVE-2021-21313: XSS on tabs

> An attacker can execute arbitrary JavaScript in the victim's browser via unsanitized parameters in the tabs endpoint, potentially stealing cookies.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h4hj-mrpg-xfgx, UBUNTU-CVE-2021-21313

## What is CVE-2021-21313?

CVE-2021-21313 is a medium-severity cross-site scripting vulnerability in Glpi-Project Glpi, published on 3 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GLPI is open source software which stands for Gestionnaire Libre de Parc Informatique and it is a Free Asset and IT Management Software package. In GLPI before verison 9.5.4, there is a vulnerability in the /ajax/common.tabs.php endpoint, indeed, at least two parameters _target and id are not properly sanitized. Here are two payloads (due to two different exploitations depending on which parameter you act) to exploit the vulnerability:/ajax/common.tabs.php?_target=javascript:alert(document.cookie)&_itemtype=DisplayPreference&_glpi_tab=DisplayPreference$2&id=258&displaytype=Ticket (Payload triggered if you click on the button). /ajax/common.tabs.php?_target=/front/ticket.form.php&_itemtype=Ticket&_glpi_tab=Ticket$1&id=(){};(function%20(){alert(document.cookie);})();function%20a&#.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2021-21313?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2021-21313?

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

## Is CVE-2021-21313 being exploited?

There is no known exploitation of CVE-2021-21313 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-2021-21313 and fix it if it is affected.

What it is: CVE-2021-21313 is a medium-severity cross-site scripting vulnerability in Glpi-Project Glpi, published on 3 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-21313 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-2021-21313/ (Markdown: https://insights.sbomify.com/CVE-2021-21313/index.md)
```

## Sources

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

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