Low

Suspended Directus user can continue to use session token to access API

  • Disclosed: 26.03.2025
  • Updated: 11.10.2026 10:22

Summary

Since the user status is not checked when verifying a session token a suspended user can use the token generated in session auth mode to access the API despite their status.

Details

There is a check missing in verifySessionJWT to verify that a user is actually still active and allowed to access the API. Right now one can extract the session token obtained by, e.g. login in to the app while still active and then, after the user has been suspended continue to use that token until it expires.

PoC

  • Create an active user
  • Log in with that user and note the session cookie
  • Suspend the user (and don't trigger an /auth/refresh call, as that invalidates the session
  • Access the API with Authorization: Bearer <token>

Impact

This weakens the security of suspending users.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package directus >= 10.10.0, < 11.5.0 11.5.0
npm package @directus/api >= 18.0.0, < 24.0.1 24.0.1
npm package @directus/types >= 11.0.7, < 13.0.0 13.0.0

References

CVSS score 3.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-672
Platform
npm
Package
directus, @directus/api, @directus/types
Disclosed
26.03.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-56p6-qw3c-fq2g - CC BY 4.0

Vulnerability history: directus

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (58) in the archive
Total entries
58
First → latest
04.2022 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 19
  • Medium 34
  • Low 3

Disclosures per year

  1. 2022: 4
  2. 2023: 8
  3. 2024: 14
  4. 2025: 17
  5. 2026: 15
Severity:
  1. High · 7.7 CVE-2026-61835 < 12.0.0 12.0.0
  2. High · 8.7 CVE-2026-35408 < 11.17.0 11.17.0
  3. High · 8.6 CVE-2025-30353 >= 9.12.0, < 11.5.0 11.5.0
  4. Suspended Directus user can continue to use session token to access API this entry
    Low · 3.5 CVE-2025-30351 >= 10.10.0, < 11.5.0 11.5.0
  5. High · 7.5 CVE-2024-54151 >= 11.0.0, < 11.3.0 11.3.0
  6. High · 7.4 CVE-2024-45596 < 10.13.3, >= 11.0.0-rc.1, < 11.1.0 10.13.3, 11.1.0
  7. High · 7.5 CVE-2024-39896 >= 9.11, < 10.13.0 10.13.0
  8. High · 6.3 CVE-2024-39701 >= 9.23.0, < 10.6.0 10.6.0
  9. High · 8.2 CVE-2024-27295 < 10.8.3 10.8.3
  10. High · 7.5 CVE-2023-45820 >= 10.4.0, < 10.6.2 10.6.2
  11. High · 7.6 ghsa-22rr-f3p8-5gf8 < 10.6.0 10.6.0
  12. Critical · 9.8 CVE-2022-26969 < 9.7.0 9.7.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.