Security readout for executives and security teams
Plain-English summary
CVE-2021-41654 describes a SQL injection flaw in Wuzhicms v4.1.0. An attacker able to reach the affected payment admin code could manipulate database queries through the keyValue parameter. The public record does not provide a CVSS score, confirmed patch, or proof of active exploitation.
Executive priority
Treat this as a targeted exposure check rather than a confirmed emergency. If Wuzhicms v4.1.0 is internet-accessible, prioritize containment and vendor-guidance review because SQL injection can threaten data confidentiality and integrity.
Technical view
The CVE states that /coreframe/app/pay/admin/index.php in Wuzhicms v4.1.0 accepts unsafe input via $keyValue, allowing arbitrary SQL commands. Available sources do not clarify authentication requirements, exploit maturity, affected CPEs, or fixed versions.
Likely exposure
Exposure is most likely limited to organizations running Wuzhicms v4.1.0, especially where the affected payment administration path is reachable. The source bundle lists no broader affected product data.
Exploitation context
CISA KEV status is false in the provided bundle, and the cited sources do not state active exploitation. The GitHub issue is the only advisory-style reference provided, so real-world exploitability details remain incomplete.
Researcher notes
Evidence is sparse: no CVSS, no CWE, no CPEs, and no fixed version are provided. Focus research on confirming authentication context, affected code reachability, and whether the GitHub issue documents a maintainer-approved fix.
Mitigation direction
- Inventory Wuzhicms deployments and identify any v4.1.0 instances.
- Check vendor or project guidance for a fixed release or official remediation.
- Restrict access to the affected payment administration path.
- Review custom deployments for unsafe handling of the keyValue parameter.
- Monitor database and web logs for suspicious activity around the affected path.
Validation and detection
- Confirm whether Wuzhicms v4.1.0 is deployed in production or staging.
- Verify whether /coreframe/app/pay/admin/index.php exists in deployed code.
- Review access controls around the affected admin payment functionality.
- Check logs for unusual requests involving the keyValue parameter.
- Track the linked GitHub issue for remediation evidence or maintainer 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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-41654 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/198CVE 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.