Security readout for executives and security teams
Plain-English summary
WUZHI CMS 4.1.0 has a stored cross-site scripting issue in the content-management feature. Malicious script could be saved in title or content fields and later run in another user's browser. The sources do not provide CVSS, patch details, or active exploitation evidence.
Executive priority
Prioritize remediation if WUZHI CMS 4.1.0 is internet-facing or accepts content from multiple users. Business impact is mainly browser-session compromise, admin targeting, and trust damage rather than direct server takeover based on available sources.
Technical view
CVE-2018-10367 describes stored XSS in WUZHI CMS 4.1.0 via title or content sections in content management. The record provides no CWE, CVSS vector, CPE mapping, or fixed version. Treat scope as limited to the described version and feature unless vendor evidence expands it.
Likely exposure
Likely exposed systems are WUZHI CMS 4.1.0 deployments where untrusted or lower-trust users can create or edit content-management titles or body content.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Public disclosure exists through a GitHub issue, but exploitability details and real-world abuse are not established here.
Researcher notes
Evidence is sparse. The CVE identifies the feature and fields, but lacks CVSS, CWE, affected CPEs, fixed version, and exploitation status. Avoid expanding affected versions without vendor or project confirmation.
Mitigation direction
- Check WUZHI CMS vendor or project guidance for a fixed version.
- Upgrade or replace WUZHI CMS 4.1.0 if a maintained release is available.
- Restrict content-management access to trusted users only.
- Ensure title and content output is safely encoded before browser rendering.
- Use CSP and monitoring as defense in depth, not as the primary fix.
Validation and detection
- Inventory all WUZHI CMS deployments and confirm version 4.1.0 exposure.
- Identify whether content-management title or content editing is enabled.
- Review rendered pages to confirm title and content output is encoded.
- Check logs for suspicious edits to titles or content fields.
- Confirm remediation against an authorized staging instance before production rollout.
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-10367 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/wuzhicms/wuzhicms/issues/135CVE 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.