GitHub Advisoryadvisory · npm

GHSA-7cvf-pxgp-42fc Directus' insufficient permission checks can enable unauthenticated users to manually trigger Flows

MEDIUM Published 2025-07-15 Modified 2025-07-15 Official page ↗
Aliases
CVE-2025-53889
Ecosystem
npm
Packages
directus
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-285, CWE-287
Reviewed
2025-07-15

Affected packages

• npm directus: < 11.9.0 → fixed in 11.9.0

Description

Summary Directus Flows with a manual trigger are not validating whether the user triggering the Flow has permissions to the items provided as payload to the Flow. Depending on what the Flow is set up to do this can lead to the Flow executing potential tasks on the attacker's behalf without authenticating. Impact Bad actors could execute the manual trigger Flows without authentication, or access rights to the said collection(s) or item(s). Users with manual trigger Flows configured are impacted as these endpoints do not currently validate if the user has read access to `directus_flows` or to the relevant collection/items. The manual trigger Flows should have tighter security requirements as compared to webhook Flows where users are expected to perform do their own checks. Workarounds Users have to implement permission checks for read access to Flows and read access to relevant collection/items.

Related

Alias · CVE (1)

  • CVE-2025-53889 Directus is a real-time API and App dashboard for managing SQL database content. vulnerability

Weakness · CWE (2)

  • CWE-285 Improper Authorization weakness
  • CWE-287 Improper Authentication weakness

References