Security readout for executives and security teams
Plain-English summary
CVE-2018-7035 is a stored cross-site scripting issue in Gleez CMS 1.2.0 and 2.0. A user could save malicious JavaScript inside HTML editor content, and it could run later when an administrator edits that content. The main business risk is administrator account compromise or unauthorized administrative actions.
Executive priority
Treat this as a targeted administrative account risk rather than a broad infrastructure emergency. Prioritize systems where untrusted users can publish or submit content that administrators later edit, especially public CMS deployments.
Technical view
The CVE describes stored XSS via HTML content submitted through an editor, demonstrated in the Add Blog flow using source editor HTML mode. The payload is stored and triggered when an Administrator edits the same content. The provided sources do not include CVSS, CWE, patch version, or confirmed exploitation.
Likely exposure
Exposure is most likely in internet-facing or internal Gleez CMS 1.2.0 and 2.0 deployments where non-admin users can create or edit HTML-rich content that administrators later review or modify.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. The GitHub issue is a public reference, so defenders should assume the vulnerability details are discoverable, but not infer real-world exploitation from the provided evidence.
Researcher notes
Evidence is limited to the CVE description and the referenced GitHub issue. No CVSS vector, CWE mapping, affected CPEs, patch version, or exploitation telemetry is present in the supplied bundle. Avoid expanding impact beyond stored XSS in Gleez CMS 1.2.0 and 2.0.
Mitigation direction
- Check Gleez CMS project guidance for a fixed version or supported migration path.
- Restrict HTML editor access to trusted users until remediation is confirmed.
- Review content moderation workflows where administrators edit user-submitted HTML.
- Apply strict output encoding and HTML sanitization where supported.
- Use CSP as defense-in-depth, not as the primary fix.
Validation and detection
- Inventory Gleez CMS deployments and confirm whether versions are 1.2.0 or 2.0.
- Identify roles allowed to submit HTML content through blog or editor workflows.
- Confirm administrator edit views do not execute stored user-supplied script content.
- Review stored blog/content records for suspicious script-like HTML.
- Check the GitHub issue and CVE record for any remediation updates.
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-7035 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/gleez/cms/issues/794CVE 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.