Security readout for executives and security teams
Plain-English summary
ExpressionEngine generated an object signing token with too little randomness. If an attacker can guess that token, the impact can escalate to remote code execution. The public bundle names affected 2.x and 3.x versions and fixed release thresholds, but does not provide CVSS scoring or evidence of active exploitation.
Executive priority
Prioritize remediation for internet-facing ExpressionEngine sites because the potential impact is remote code execution. Urgency is high for unpatched legacy deployments, but the evidence provided does not establish active exploitation or a CVSS severity score.
Technical view
CVE-2017-0897 is a CWE-330 weakness in ExpressionEngine before 2.11.8 and 3.5.5. Weak entropy in an object signing token can undermine trust in signed objects, with successful guessing leading to remote code execution. Available sources identify fixed versions but do not include exploit telemetry.
Likely exposure
Exposure is most likely on legacy ExpressionEngine installations still running 2.x before 2.11.8 or 3.x before 3.5.5. Public internet-facing CMS deployments should be prioritized because the stated worst-case impact is remote code execution.
Exploitation context
The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. A HackerOne report is referenced, indicating public vulnerability disclosure history, but the supplied details do not support claims of exploitation in the wild.
Researcher notes
The key technical issue is insufficient entropy in an object signing token. Validation should focus on version confirmation and exposure mapping, not speculative exploitability. Source evidence is limited to affected version ranges, CWE classification, and public references.
Mitigation direction
- Upgrade ExpressionEngine 2.x installations to 2.11.8 or later.
- Upgrade ExpressionEngine 3.x installations to 3.5.5 or later.
- Review ExpressionEngine release notes for version-specific upgrade guidance.
- Retire unsupported legacy ExpressionEngine instances where upgrades are not feasible.
- Monitor affected sites for unexplained file, template, or administrator changes.
Validation and detection
- Inventory all ExpressionEngine sites and record exact versions.
- Flag 2.x versions below 2.11.8 as vulnerable.
- Flag 3.x versions below 3.5.5 as vulnerable.
- Confirm upgraded instances report fixed or later versions.
- Review web and application logs for suspicious administrative or code changes.
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-330: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-0897 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://docs.expressionengine.com/v2/about/changelog.html#version-2-11-8CVE reference · x_refsource_CONFIRM
- https://hackerone.com/reports/215890CVE reference · x_refsource_MISC
- https://docs.expressionengine.com/latest/about/changelog.html#version-3-5-5CVE reference · x_refsource_CONFIRM
- https://expressionengine.com/blog/expressionengine-3.5.5-and-2.11.8-releasedCVE 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.
Use of Insufficiently Random Values
Use of Insufficiently Random Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.