CVE-2020-37222: Kuicms Php EE 2.0 Persistent Cross-Site Scripting via bbs reply
Kuicms Php EE 2.0 contains a persistent cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts by submitting crafted content through the bbs reply endpoint. Attackers can send POST requests to /web/?c=bbs&a=reply with HTML and JavaScript payloads in the content parameter to execute arbitrary scripts in users' browsers.
Security readout for executives and security teams
Plain-English summary
CVE-2020-37222 is a stored cross-site scripting issue in Kuicms Php EE 2.0. An unauthenticated attacker can place malicious browser script into BBS replies, which may later run for users viewing that content. The main business risk is account/session compromise, trusted-site abuse, and reputational impact on affected public sites.
Executive priority
Treat this as a high-priority web application exposure if Kuicms Php EE 2.0 is deployed publicly. Public exploit information raises urgency, but no source here confirms active exploitation or a vendor fix.
Technical view
Kuicms Php EE 2.0 is reported vulnerable to persistent XSS in the BBS reply path, tied to unsafely handled reply content. The CVSS 3.1 score is 7.2 with network access, low complexity, no privileges, changed scope, and low confidentiality and integrity impact. Sources do not identify a vendor patch.
Likely exposure
Exposure is most likely on internet-facing Kuicms Php EE 2.0 deployments with the BBS reply functionality reachable. Organizations not running Kuicms Php EE 2.0, or without reachable BBS reply handling, are not indicated as affected by the provided sources.
Exploitation context
The bundle cites a public ExploitDB entry and VulnCheck advisory, so exploit information is public. CISA KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Keep analysis scoped to Kuicms Php EE 2.0. The sources identify CWE-79 stored XSS through BBS reply content and provide CVSS details, but they do not provide confirmed patch status, affected version ranges beyond 2.0, or KEV-backed exploitation evidence.
Mitigation direction
Identify and prioritize any Kuicms Php EE 2.0 deployments.
Check vendor guidance or replacement options; no patch is named in the provided sources.
Restrict or disable public BBS reply submission where business permits.
Ensure user-supplied reply content is safely encoded before rendering.
Review and remove suspicious existing BBS reply content.
Validation and detection
Confirm whether Kuicms Php EE 2.0 is deployed and internet reachable.
Verify whether the BBS reply route is accessible to unauthenticated users.
Inspect stored replies for unexpected script-like markup or HTML abuse.
Review web, CDN, and WAF logs for unusual BBS reply submissions.
Validate that rendered replies neutralize user-supplied HTML and JavaScript.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.