Security readout for executives and security teams
Plain-English summary
CVE-2017-11128 is a stored cross-site scripting issue reported in Bolt CMS 3.2.14. A saved text field, demonstrated with a New Entry title, may store unsafe scriptable content that later affects viewers. Business risk depends on whether the vulnerable CMS version is still deployed and who can create or edit entries.
Executive priority
Prioritize review if Bolt CMS is internet-facing, supports multiple content editors, or allows less-trusted users to create entries. This is not backed by active exploitation evidence in the bundle, but stored XSS can affect administrator sessions and site trust.
Technical view
The public description says Bolt CMS 3.2.14 allows stored XSS through text input, demonstrated in the New Entry Title field. The bundle provides no CVSS score, CWE, fixed version, or vendor mitigation. Treat exposure as content-rendering sanitization failure until confirmed against the deployed Bolt version and templates.
Likely exposure
Likely exposure is limited to organizations still running Bolt CMS 3.2.14 or closely related unverified builds. Practical risk is higher where untrusted or low-privilege users can create or edit CMS entries.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation appears to require saving malicious content into an affected text field, then having another user view the stored content. That access requirement should be validated locally.
Researcher notes
Evidence is sparse: the CVE description and one external reference identify Bolt CMS 3.2.14 and a stored XSS demonstration in the Title field. No patch, CVSS vector, affected CPE, or exploit prevalence is provided, so avoid broader product or version claims.
Mitigation direction
- Identify any deployed Bolt CMS 3.2.14 instances.
- Check current Bolt vendor guidance for fixed versions or recommended upgrades.
- Restrict entry creation and editing to trusted users only.
- Review templates and rendering paths for proper HTML escaping.
- Remove or sanitize suspicious stored entry titles and text fields.
Validation and detection
- Inventory CMS versions across production, staging, and backups.
- Confirm whether New Entry Title output is HTML-encoded when rendered.
- Review CMS audit logs for unusual entry title or text-field changes.
- Check whether non-admin users can create or edit entries.
- Document whether vendor guidance names an upgrade or mitigation.
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-2017-11128 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://websecnerd.blogspot.in/2017/07/bolt-cms-3.htmlCVE 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.