Security readout for executives and security teams
Plain-English summary
CVE-2018-17425 is a stored cross-site scripting issue reported in WUZHI CMS 4.1.0. Content entered into the Membership Center “I want to ask” detailed description field may be stored and later rendered unsafely, allowing attacker-controlled script execution in another user’s browser.
Executive priority
Treat this as a targeted web application risk, not an internet-wide emergency. Prioritize if WUZHI CMS 4.1.0 is public-facing, accepts member submissions, or is used by privileged administrators.
Technical view
The CVE describes stored XSS under index.php?m=member in WUZHI CMS 4.1.0, specifically the Membership Center question detail field. Public metadata does not provide CVSS, CWE mapping, confirmed affected CPEs, exploit maturity, or a named vendor fix.
Likely exposure
Exposure is most likely where WUZHI CMS 4.1.0 is deployed and the member question submission workflow is reachable by untrusted or low-trust users.
Exploitation context
CISA KEV is false in the supplied bundle, and the provided sources do not state active exploitation. Stored XSS can still matter because malicious content may persist and execute when administrators or users view it.
Researcher notes
The public bundle is sparse: one GitHub issue reference, no CVSS vector, no CWE, no CPEs, and no confirmed patch details. Validate exposure directly against deployed WUZHI CMS version and feature usage.
Mitigation direction
- Check WUZHI CMS vendor or project guidance for a fixed release or patch.
- Restrict access to the affected member question workflow until remediation is confirmed.
- Encode user-supplied description content when rendering pages.
- Sanitize stored member-submitted content according to application policy.
- Review existing submitted descriptions for unexpected HTML or script-like content.
Validation and detection
- Inventory WUZHI CMS deployments and confirm whether version 4.1.0 is present.
- Determine whether index.php?m=member and Membership Center submissions are enabled.
- Verify that stored description text renders as inert content in staging.
- Review logs and content history for suspicious member question submissions.
- Confirm any applied vendor fix against the affected workflow.
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-17425 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/153CVE 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.