Security readout for executives and security teams
Plain-English summary
October CMS versions before 1.0.473 and 1.1.6 allowed a logged-in backend user to run PHP through theme import, bypassing template safe mode. For affected self-hosted sites, a compromised or malicious backend account could become full server-side code execution.
Executive priority
Prioritize remediation for any internet-facing or business-critical October CMS instance with multiple backend users. The issue needs prompt action because low-privileged backend access can lead to full server-side code execution.
Technical view
The flaw is CWE-74 injection in october/system theme import handling. CVSS 3.1 is 8.8: network reachable, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact. The vendor patched it in Build 473 and v1.1.6.
Likely exposure
Exposure is limited to October CMS installations running <1.0.473 or >=1.1.0 and <1.1.6 where an attacker has backend access. Public internet exposure increases business risk, but the source bundle does not state unauthenticated exploitation.
Exploitation context
The provided sources say exploitation requires backend access and uses the theme import feature to execute PHP despite safe mode. CISA KEV is false in the bundle, and no cited source confirms active exploitation.
Researcher notes
Key validation should focus on version, patch state, backend account exposure, and theme import audit evidence. Do not assume unauthenticated reachability or active exploitation from the supplied sources; the known precondition is backend access.
Mitigation direction
- Upgrade October CMS to Build 473, v1.0.473, v1.1.6, or later.
- If unable to upgrade, apply the vendor patch manually.
- Review the GitHub advisory before planning remediation.
- Restrict backend access to trusted accounts only.
- Remove unnecessary backend users and permissions.
Validation and detection
- Inventory October CMS versions across all self-hosted sites.
- Confirm affected versions are not present in production or staging.
- Verify the vendor patch or fixed build is installed.
- Review backend user access for unexpected or excessive privileges.
- Check available logs for recent theme import 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.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32650 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/octobercms/october/security/advisories/GHSA-5hfj-r725-wpc4CVE reference · x_refsource_CONFIRM
- https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26CVE 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.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.