Security readout for executives and security teams
Plain-English summary
This issue affects Creditwest Bank CMS Project, also called CWCMS, through 2017-07-28. A victim administrator could be tricked into changing site configuration, potentially allowing PHP code injection. Business urgency depends on whether this old CMS code is still deployed.
Executive priority
Prioritize assessment if CWCMS is internet-facing or business-critical. The potential impact is severe, but urgency is conditional because affected product metadata and patch status are incomplete.
Technical view
CVE-2018-8972 describes CSRF in the site configuration update function of CWCMS through 2017-07-28. The reported impact is arbitrary PHP code injection. The public metadata does not provide CVSS, CWE, CPEs, or a named fixed version.
Likely exposure
Exposure appears limited to organizations running Creditwest Bank CMS Project/CWCMS through 2017-07-28. The CVE record lists affected vendor and product as n/a, so asset confirmation is required.
Exploitation context
The CVE references a public GitHub issue describing the vulnerability. There is no KEV listing in the supplied bundle, and no cited source here confirms active exploitation.
Researcher notes
The strongest technical signal is the referenced GitHub issue. The source bundle lacks CVSS, CWE, CPE, and fixed-version data, so avoid broad product claims. Treat findings as CWCMS-specific until validated.
Mitigation direction
- Identify whether any public or internal sites run CWCMS.
- Check the project repository or vendor guidance for a fixed revision.
- Isolate or retire affected CWCMS deployments if no maintained fix exists.
- Restrict administrative access while remediation is assessed.
- Review configuration integrity before returning systems to service.
Validation and detection
- Inventory web assets for CWCMS code or branding.
- Confirm deployed source date or commit is after vendor-fixed guidance, if available.
- Review configuration files for unexpected PHP content.
- Check admin and web logs for suspicious configuration changes.
- Verify CSRF protections exist on configuration update actions.
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-2018-8972 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/CREDITWEST/CWCMS/issues/1CVE 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.