# CVE-2025-53885: Directus doesn't redact sensitive user data when logging via event hooks


- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 14 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-x3vm-88hf-gpxp

## What is CVE-2025-53885?

CVE-2025-53885 is a medium-severity vulnerability in Monospace Directus, published on 14 Jul 2025. 

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.0.0 and prior to version 11.9.0, when using Directus Flows to handle CRUD events for users it is possible to log the incoming data to console using the "Log to Console" operation and a template string. Malicious admins can log sensitive data from other users when they are created or updated. Version 11.9.0 contains a fix for the issue. As a workaround, avoid logging sensitive data to the console outside the context of development.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-53885?

2 open source packages ship an affected version, including directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | From 9.0.0 | 11.9.0 |
| `directus` | npm | From 9.0.0 | 11.9.0 |

Products: Monospace Directus.

## How do I fix CVE-2025-53885?

Upgrade directus to 11.9.0 or later.

## Is CVE-2025-53885 being exploited?

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

What it is: CVE-2025-53885 is a medium-severity vulnerability in Monospace Directus, published on 14 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-53885 in the wild and no public exploit code.

Affected packages and fixed versions:
- directus (npm): affected from 9.0.0; fixed in 11.9.0
- directus (npm): affected from 9.0.0; fixed in 11.9.0

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

## Sources

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

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