Security readout for executives and security teams
Plain-English summary
This CVE describes a privacy failure in Directus 7 API through 2.3.0. Image files meant to be non-public may still be readable if someone knows or guesses the filename path under uploads/_/originals/. Business impact depends on whether private or regulated images were stored there.
Executive priority
Treat this as a targeted data exposure risk, not a platform-wide compromise signal. Prioritize if Directus handled confidential customer, employee, medical, identity, or contractual images. If only public images were stored, urgency is lower.
Technical view
Directus 7 API through 2.3.0 allowed remote reads of image originals by direct filename request under uploads/_/originals/. The issue is tied to a non-public file collection option not applying to the thumbnailer path. No CVSS, CWE, vendor patch note, or confirmed exploit evidence is included in the provided sources.
Likely exposure
Exposure is most likely where Directus 7 API through 2.3.0 stores sensitive images and serves uploads/_/originals/ from a reachable web path. The sources do not identify other affected products or versions.
Exploitation context
The source description indicates remote unauthenticated file reads may be possible by direct filename request. There is no KEV listing and no provided source confirming active exploitation, public exploit use, or scanning activity.
Researcher notes
The evidence is sparse: the CVE record names the affected Directus API line and vulnerable path behavior, but provides no CVSS, CWE, exploit confirmation, or explicit remediation. Validation should focus on version, path exposure, and whether private image assumptions were incorrect.
Mitigation direction
- Inventory any Directus 7 API deployments at or below 2.3.0.
- Check Directus project guidance for a fixed version or official configuration change.
- Do not rely on non-public file collection settings to protect image originals.
- Restrict public reachability of uploads/_/originals/ where sensitive images may exist.
- Review exposed image content and rotate or remove sensitive files as needed.
Validation and detection
- Confirm the Directus API version in each deployment.
- Review routing, CDN, and storage exposure for uploads/_/originals/.
- Test access control behavior using non-sensitive image filenames only.
- Check whether private file collection settings protect originals as intended.
- Review logs for unusual direct requests to image original paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-13981 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/directus/api/issues/987CVE reference · x_refsource_MISC
- https://github.com/directus/api/issues/986CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.