# CVE-2024-28238: Directus session token exposure in URL on files page

Source: https://junglewise.ai/threats/cve-2024-28238-directus-session-token-exposure-in-url-on-files-page  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-03-12. Updated: 2026-05-14  
License: CC BY 4.0 with a link back

CVE-2024-28238 · Severity: low · CVSS 3.1 · Published 2024-03-12

Directus, a platform used to manage database content and power custom applications, was found to expose user session tokens within website addresses (URLs) on its files page. If an unauthorized person gains access to server logs or a user's browser history, they could potentially use these tokens to hijack an active session. This could allow them to view sensitive information or perform actions as if they were the legitimate user.

Technologies: [directus (npm)](https://junglewise.ai/threats/technologies/directus). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2024-28238 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-28238 being exploited in the wild.

**How severe is CVE-2024-28238?** Low severity, with a CVSS score of 3.1, published 12 March 2024.

**Which products and versions are affected?** directus (npm) SEMVER:introduced=0,fixed=10.10.0.

**Is there a fix for CVE-2024-28238?** Yes. directus (npm): upgrade to 10.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2024-28238 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2024-28238?** Check whether you run directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- directus (npm): upgrade to 10.10.0 or later

  ```sh
  npm install directus@10.10.0
  ```


## Technical details

A vulnerability exists in Directus where the application uses the HTTP GET method to pass sensitive JSON Web Tokens (JWT) in the URL query string when navigating to the /files page. This violates security best practices (CWE-598) as URLs are frequently recorded in plaintext within web server logs, proxy logs, and browser history. An attacker with local access or administrative privileges to these logs could extract the session token to impersonate users. The issue is fixed in version 10.10.0 by ensuring tokens are no longer transmitted via GET parameters.

## Affected products

- Directus directus < 10.10.0

## Identifiers

- CVE-2024-28238
- GHSA-2ccr-g2rv-h677

## Timeline

- 2024-03-12: advisory: GitHub Security Advisory published
- 2024-03-12: patched: Fix released in version 10.10.0

## References

- [https://github.com/directus/directus/security/advisories/GHSA-2ccr-g2rv-h677](https://github.com/directus/directus/security/advisories/GHSA-2ccr-g2rv-h677)
- [https://github.com/directus/directus](https://github.com/directus/directus)

## Related threats

- [Directus authorization bypass via unsegmented response cache key](https://junglewise.ai/threats/cve-2026-61836-directus-authorization-bypass-via-unsegmented-response-cache-key)
- [Directus SSRF bypass in file import via 0.0.0.0 address](https://junglewise.ai/threats/cve-2026-61835-directus-ssrf-bypass-in-file-import-via-0-0-0-0-address)
- [Directus sensitive information disclosure via aggregate queries](https://junglewise.ai/threats/cve-2026-35442-directus-sensitive-information-disclosure-via-aggregate-queries)
- [Directus resource exhaustion via GraphQL alias amplification](https://junglewise.ai/threats/cve-2026-35441-directus-resource-exhaustion-via-graphql-alias-amplification)
- [Directus GraphQL introspection bypass in system endpoint](https://junglewise.ai/threats/cve-2026-35413-directus-graphql-introspection-bypass-in-system-endpoint)