Security readout for executives and security teams
Plain-English summary
An unpatched October CMS site can let certain trusted backend editors bypass Safe Mode and run PHP through CMS templates. The risk is limited to authenticated users with specific CMS editing permissions, but it matters where Safe Mode was used to separate content editing from code execution.
Executive priority
Prioritize remediation where October CMS is internet-facing, production-critical, or has multiple backend editors. The vulnerability is not broadly unauthenticated, but it undermines an administrative safety boundary and can turn template-editing access into code execution.
Technical view
October CMS versions 1.0.319 to before 1.0.469 allowed a Twig sandbox escape when cms.enableSafeMode was enabled. Backend users with cms.manage_pages, cms.manage_layouts, or cms.manage_partials could craft Twig content that escaped the intended restriction and executed arbitrary PHP. Patched in Build 469 and v1.1.0.
Likely exposure
Exposure is mainly self-hosted October CMS deployments running affected 1.0.x builds with Safe Mode enabled and backend users allowed to edit pages, layouts, or partials. Sites that already trust those users to write PHP are less affected by the stated security boundary.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated backend access, high privileges, and user interaction, but could impact confidentiality, integrity, and availability once PHP execution is reached.
Researcher notes
The key control failure is a Twig sandbox escape under Safe Mode, mapped to CWE-862 in the source bundle. Assessment should focus on version, Safe Mode reliance, backend role assignments, and whether template editors are intentionally trusted with PHP execution.
Mitigation direction
- Upgrade October CMS to Build 469, v1.0.469, v1.1.0, or later.
- Review vendor advisory and release guidance before production rollout.
- Audit backend accounts with CMS page, layout, or partial editing permissions.
- Remove CMS template editing permissions from users who should not execute PHP.
- Review recent CMS template changes made by privileged backend users.
Validation and detection
- Inventory October CMS versions across self-hosted environments.
- Confirm whether cms.enableSafeMode is enabled on affected deployments.
- List users with cms.manage_pages, cms.manage_layouts, or cms.manage_partials permissions.
- Verify the deployed build is 469 or later.
- Check change history for suspicious page, layout, or partial edits.
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.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-15247 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
- Medium
- CVSS
- 5.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.13.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/octobercms/october/security/advisories/GHSA-94vp-rmqv-5875CVE reference · x_refsource_CONFIRM
- https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982CVE 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.