Security readout for executives and security teams
Plain-English summary
Monstra CMS 3.0.4 allowed stored cross-site scripting through the page Name field in the admin page-creation workflow. A malicious value could be saved and later executed in a browser. Business impact depends on who can access that admin function and whether the CMS is still deployed.
Executive priority
Address during normal vulnerability remediation unless the CMS admin area is internet-exposed, shared with untrusted users, or supports sensitive operations. Escalate if Monstra CMS 3.0.4 is still public-facing or unsupported.
Technical view
The CVE describes stored XSS in Monstra CMS 3.0.4 at admin/index.php?id=pages, related to plugins/box/pages/pages.admin.php. The vulnerable input is the Name field on Create New Page. The source bundle provides no CVSS score, CWE mapping, patch version, or vendor mitigation details.
Likely exposure
Exposure is likely limited to sites running Monstra CMS 3.0.4 where an attacker has access to the admin page-creation workflow, or can influence someone with that access. The bundle does not identify other affected versions or products.
Exploitation context
A public Exploit-DB reference exists, so public technical details were available. The source bundle does not show CISA KEV listing or other evidence of active exploitation. Treat this as a public stored-XSS issue, not a confirmed actively exploited vulnerability.
Researcher notes
Evidence is narrow: the CVE description, GitHub issue, and Exploit-DB reference identify stored XSS in one admin workflow. The bundle does not provide CVSS, CWE, patch status, or a confirmed affected-version range beyond Monstra CMS 3.0.4.
Mitigation direction
- Inventory any Monstra CMS deployments and confirm exact versions.
- Check vendor or project guidance for fixed versions or maintained replacements.
- Restrict admin access to trusted users and trusted networks where possible.
- Review existing page names for suspicious HTML or script-like content.
- Apply output encoding or input sanitization only through supported, tested code changes.
Validation and detection
- Confirm whether Monstra CMS 3.0.4 is present in production or backups.
- Review access controls for admin/index.php?id=pages.
- Inspect page Name values for unexpected markup or script indicators.
- Check plugins/box/pages/pages.admin.php handling of saved page names.
- Validate any fix in staging before production release.
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-10118 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/monstra-cms/monstra/issues/436CVE reference · x_refsource_MISC
- 44855CVE reference · exploit, x_refsource_EXPLOIT-DB
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.