# CVE-2025-30353: Directus's webhook trigger flows can leak sensitive data

> Attackers can leak sensitive environment variables and API keys via webhook flows when validation errors occur in Directus.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-fm3h-p9wm-h74h

## What is CVE-2025-30353?

CVE-2025-30353 is a high-severity vulnerability in Monospace Directus, published on 26 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.12.0 and prior to version 11.5.0, when a Flow with the "Webhook" trigger and the "Data of Last Operation" response body encounters a ValidationError thrown by a failed condition operation, the API response includes sensitive data. This includes environmental variables, sensitive API keys, user accountability information, and operational data. This issue poses a significant security risk, as any unintended exposure of this data could lead to potential misuse. Version 11.5.0 fixes the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | From 9.12.0 | 11.5.0 |
| `directus` | npm | From 9.12.0 | 11.5.0 |

Products: Monospace Directus.

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

Upgrade directus to 11.5.0 or later.

## Is CVE-2025-30353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30353 exists.

## 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-2026-39942](https://insights.sbomify.com/CVE-2026-39942/): Directus has a Path Traversal and Broken Access Control in File Management API (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30353 and fix it if it is affected.

What it is: CVE-2025-30353 is a high-severity vulnerability in Monospace Directus, published on 26 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30353 exists.

Affected packages and fixed versions:
- directus (npm): affected from 9.12.0; fixed in 11.5.0
- directus (npm): affected from 9.12.0; fixed in 11.5.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-30353/ (Markdown: https://insights.sbomify.com/CVE-2025-30353/index.md)
```

## Sources

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

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