# CVE-2024-54128: Directus has an HTML Injection in Comment

> Attacker can inject HTML via comments due to client-side filtering bypass, potentially leading to script execution or account takeover.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Dec 2024
- **Updated:** 6 Dec 2024
- **Also known as:** GHSA-r6wx-627v-gh2f

## What is CVE-2024-54128?

CVE-2024-54128 is a medium-severity cross-site scripting vulnerability in Monospace Directus, published on 5 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. The Comment feature has implemented a filter to prevent users from adding restricted characters, such as HTML tags. However, this filter operates on the client-side, which can be bypassed, making the application vulnerable to HTML Injection. This vulerability is fixed in 10.13.4 and 11.2.0.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2024-54128?

6 open source packages ship an affected version, including directus and @directus/app. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | From 10.10.0 | 10.13.4 |
| `directus` | npm | From 10.10.0 | 10.13.4 |
| `directus` | npm | From 11.0.0-rc.1 | 11.2.2 |
| `directus` | npm | From 11.0.0-rc.1 | 11.2.2 |
| `@directus/app` | npm | From 11.0.0 | 13.3.1 |
| `@directus/app` | npm | From 11.0.0 | 13.3.1 |

Products: Monospace Directus.

## How do I fix CVE-2024-54128?

Upgrade directus to a fixed version for your release line: 10.13.4 or 11.2.2.

## Is CVE-2024-54128 being exploited?

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

## Other vulnerabilities in Monospace Directus

- [CVE-2022-26969](https://insights.sbomify.com/CVE-2022-26969/): Insecure default value for CORS configuration (critical 9.8)
- [CVE-2025-55746](https://insights.sbomify.com/CVE-2025-55746/): Directus allows unauthenticated file upload and file modification due to lacking input sanitization (critical 9.3)
- [CVE-2026-35408](https://insights.sbomify.com/CVE-2026-35408/): Directus is Missing Cross-Origin Opener Policy (high 8.7)
- [CVE-2026-61836](https://insights.sbomify.com/CVE-2026-61836/): Directus: Authorization-dependent response served from unsegmented cache key (high 8.6)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54128 and fix it if it is affected.

What it is: CVE-2024-54128 is a medium-severity cross-site scripting vulnerability in Monospace Directus, published on 5 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-54128 in the wild and no public exploit code.

Affected packages and fixed versions:
- directus (npm): affected from 10.10.0; fixed in 10.13.4
- directus (npm): affected from 10.10.0; fixed in 10.13.4
- directus (npm): affected from 11.0.0-rc.1; fixed in 11.2.2
- directus (npm): affected from 11.0.0-rc.1; fixed in 11.2.2
- @directus/app (npm): affected from 11.0.0; fixed in 13.3.1
- @directus/app (npm): affected from 11.0.0; fixed in 13.3.1

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-2024-54128/ (Markdown: https://insights.sbomify.com/CVE-2024-54128/index.md)
```

## Sources

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

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