# CVE-2026-53987: Tag Plugin for GLPI 11 before 2.14.4 Stored Cross-Site Scripting in Kanban Badge Rendering

> Authenticated users can inject malicious scripts via tag names that execute in other users' browsers when viewing Kanban boards.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-6rpj-89c7-x2mh, GHSA-qc6r-wrm6-23pm

## What is CVE-2026-53987?

CVE-2026-53987 is a high-severity cross-site scripting vulnerability in pluginsGLPI tag, published on 9 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Tag plugin for GLPI 11 before 2.14.4 stores the tag name without HTML sanitization and renders it into the Kanban badge markup via PluginTagTag::preKanbanContent() without output escaping, resulting in stored cross-site scripting. An authenticated user with TAG MANAGEMENT create or update rights can set a tag name containing HTML, which then executes in the browser of any user who opens the Kanban view of a ticket, problem, change, or project the tag is attached to.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-53987?


## How do I fix CVE-2026-53987?

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

## Is CVE-2026-53987 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53987 and fix it if it is affected.

What it is: CVE-2026-53987 is a high-severity cross-site scripting vulnerability in pluginsGLPI tag, published on 9 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53987 in the wild and no public exploit code.

Affected product: pluginsGLPI tag. 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-2026-53987/ (Markdown: https://insights.sbomify.com/CVE-2026-53987/index.md)
```

## Sources

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

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