NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

highCVSS 3.1 8.6GHSA-fm3h-p9wm-h74h

Describe the Bug In Directus, 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.

Published Mar 26, 2025

Affected packages

directus

Ecosystem
npm
Affected
>= 9.12.0, < 11.5.0
Fixed in
11.5.0
Check
npm ls directus

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Describe the Bug

In Directus, 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.

Image Image Image

To Reproduce

Steps to Reproduce:

  1. Create a Flow in Directus with:
  2. Trigger: Webhook
  3. Response Body: Data of Last Operation
  4. Add a condition that is likely to fail.
  5. Trigger the Flow with any input data that will fail the condition.
  6. Observe the API response, which includes sensitive information like:
  7. Environmental variables ($env)
  8. Authorization headers
  9. User details under $accountability
  10. Previous operational data.

Expected Behavior: In the event of a ValidationError, the API response should only contain relevant error messages and details, avoiding the exposure of sensitive data.

Actual Behavior: The API response includes sensitive information such as:

  • Environment keys (FLOWS_ENV_ALLOW_LIST)
  • User accountability (role, user, etc.)
  • Operational logs (current_payments, $last), which might contain private details.

Credited to dzevs.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries