Directus exposes sensitive fields in revision history
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| directus | directus | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Directus | Directus |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mvv8-v4jj-g47j | Directus: Sensitive fields exposed in revision history |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.173% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Monospace
Monospace directus |
|
| CPEs | cpe:2.3:a:monospace:directus:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Monospace
Monospace directus |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Directus
Directus directus |
|
| Vendors & Products |
Directus
Directus directus |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, Directus stores revision records (in directus_revisions) whenever items are created or updated. Due to the revision snapshot code not consistently calling the prepareDelta sanitization pipeline, sensitive fields (including user tokens, two-factor authentication secrets, external auth identifiers, auth data, stored credentials, and AI provider API keys) could be stored in plaintext within revision records. This vulnerability is fixed in 11.17.0. | |
| Title | Directus exposes sensitive fields in revision history | |
| Weaknesses | CWE-200 CWE-312 |
|
| References |
| |
| Metrics |
cvssV3_1
|