Loading vulnerability…
CVE-2025-53889 affects Directus, a real-time API and app dashboard for managing SQL database content. In Directus versions starting at 9.12.0 and before 11.9.0, Flows configured with a manual trigger do not properly validate whether the user invoking the Flow has permission to the items supplied in the Flow payload. The vulnerable behavior also fails to ensure the caller has appropriate read access to directus_flows and to the relevant collections or items referenced by the request. As a result, a manual trigger Flow can be executed against data the caller is not authorized to access, and the Flow may perform configured actions on the attacker's behalf without proper authorization checks. The issue is specific to manual trigger Flows and stems from missing authorization enforcement on the trigger endpoint and associated payload items.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.