Security readout for executives and security teams
Plain-English summary
This Drupal Core issue can let access controls be bypassed through JSON:API, but only on sites where JSON:API is configured for read/write mode. Affected branches are 8.8.x before 8.8.8, 8.9.x before 8.9.1, and 9.0.x before 9.0.1.
Executive priority
Prioritize verification for any internet-facing Drupal site running affected versions with JSON:API write mode enabled. Urgency is configuration-dependent, and the provided sources do not establish active exploitation or a quantified severity score.
Technical view
CVE-2020-13665 is an access bypass in Drupal Core tied to JSON:API when jsonapi.settings has read_only set to FALSE. The provided sources identify vulnerable Drupal Core 8.8.x, 8.9.x, and 9.0.x versions before the fixed releases, but do not provide CVSS, CWE, exploit details, or impact scope.
Likely exposure
Exposure appears limited to Drupal sites on the affected versions that enabled JSON:API write capability by setting read_only to FALSE. Sites using default read-only JSON:API settings are not identified as vulnerable in the provided description.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or exploitation prerequisites beyond the vulnerable JSON:API configuration. Treat internet-facing affected Drupal sites as needing prompt verification.
Researcher notes
Key unknowns are impact boundaries, affected permission paths, CVSS, and exploit status. Validation should focus on version, jsonapi.settings read_only state, and whether JSON:API write operations were exposed before remediation.
Mitigation direction
- Upgrade Drupal Core to 8.8.8, 8.9.1, 9.0.1, or later supported releases.
- Confirm jsonapi.settings read_only is not FALSE unless business-required.
- Review Drupal advisory SA-CORE-2020-006 for vendor-specific remediation details.
- Restrict unauthenticated or unnecessary JSON:API exposure where feasible.
- Prioritize supported Drupal versions for long-term security maintenance.
Validation and detection
- Inventory Drupal Core versions across production, staging, and public-facing assets.
- Check jsonapi.settings for read_only set to FALSE.
- Confirm JSON:API module exposure on affected Drupal sites.
- Verify deployed versions are at or beyond the fixed release thresholds.
- Review recent JSON:API access logs for unusual unauthorized activity.
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-2020-13665 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://www.drupal.org/sa-core-2020-006CVE reference · x_refsource_CONFIRM
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.