# CVE-2025-24353: Directus privilege escalation vulnerability using Share feature

> A privilege escalation flaw in Directus allows users to view restricted fields by specifying arbitrary roles in the share feature.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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:** 23 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-pmf4-v838-29hg

## What is CVE-2025-24353?

CVE-2025-24353 is a medium-severity vulnerability in Monospace Directus, published on 23 Jan 2025. 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. Prior to version 11.2.0, when sharing an item, a typical user can specify an arbitrary role. It allows the user to use a higher-privileged role to see fields that otherwise the user should not be able to see. Instances that are impacted are those that use the share feature and have specific roles hierarchy and fields that are not visible for certain roles. Version 11.2.0 contains a patch the issue.

Weakness: CWE-269 (Improper Privilege Management)

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

4 open source packages ship an affected version, including @directus/app and directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@directus/app` | npm | All versions | 13.3.1 |
| `@directus/app` | npm | All versions | 13.3.1 |
| `directus` | npm | All versions | 11.2.0 |
| `directus` | npm | All versions | 11.2.0 |

Products: Monospace Directus.

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

Upgrade @directus/app to 13.3.1 or later.

## Is CVE-2025-24353 being exploited?

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

What it is: CVE-2025-24353 is a medium-severity vulnerability in Monospace Directus, published on 23 Jan 2025. 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-2025-24353 exists.

Affected packages and fixed versions:
- @directus/app (npm): affected all versions; fixed in 13.3.1
- @directus/app (npm): affected all versions; fixed in 13.3.1
- directus (npm): affected all versions; fixed in 11.2.0
- directus (npm): affected all versions; fixed in 11.2.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-24353/ (Markdown: https://insights.sbomify.com/CVE-2025-24353/index.md)
```

## Sources

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

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