# CVE-2024-39701: Directus Incorrectly handles _in` filter

> Attackers can bypass access control rules by exploiting improper handling of empty arrays in filter operators, allowing unauthorized data access.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-hxgm-ghmv-xjjm

## What is CVE-2024-39701?

CVE-2024-39701 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 8 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Directus >=9.23.0, <=v10.5.3 improperly handles _in, _nin operators. It evaluates empty arrays as valid so expressions like {"role": {"_in": $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass. This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. This vulnerability is fixed in 10.6.0.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-39701?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | From 9.23.0 | 10.6.0 |
| `directus` | npm | From 9.23.0 | 10.6.0 |

Products: Monospace Directus.

## How do I fix CVE-2024-39701?

Upgrade directus to 10.6.0 or later.

## Is CVE-2024-39701 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39701 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-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-2024-39701 and fix it if it is affected.

What it is: CVE-2024-39701 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 8 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39701 exists.

Affected packages and fixed versions:
- directus (npm): affected from 9.23.0; fixed in 10.6.0
- directus (npm): affected from 9.23.0; fixed in 10.6.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-2024-39701/ (Markdown: https://insights.sbomify.com/CVE-2024-39701/index.md)
```

## Sources

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

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