LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11528: WUZHI CMS 4.1.0 has SQL Injection via an api/sms_check.php?param= URI.

WUZHI CMS 4.1.0 has SQL Injection via an api/sms_check.php?param= URI.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-11528 is a reported SQL injection in WUZHI CMS 4.1.0 involving the api/sms_check.php param URI parameter. If a vulnerable site exposes this endpoint, attackers may be able to interfere with database queries. The source bundle does not provide CVSS, confirmed impact details, or a vendor fix.

Executive priority

Prioritize identification and containment for any internet-facing WUZHI CMS 4.1.0 instance. The vulnerability class can threaten database confidentiality and integrity, but the available sources do not prove active exploitation or name an official patch.

Technical view

The CVE description identifies SQL injection in WUZHI CMS 4.1.0 through api/sms_check.php?param=. The available sources are limited to the CVE records and a GitHub issue reference. No CWE, CVSS vector, affected CPE, patch version, or detailed remediation is provided in the bundle.

Likely exposure

Exposure is likely limited to deployments running WUZHI CMS 4.1.0 with the api/sms_check.php endpoint reachable, especially internet-facing CMS installations. The bundle does not identify other versions or products as affected.

Exploitation context

The issue is publicly disclosed through CVE records and a GitHub issue. The source bundle does not show CISA KEV listing, active exploitation, public exploit maturity, or observed attacks. Treat exploitation status as unconfirmed.

Researcher notes

The public record is sparse: description, affected version, endpoint, and parameter are known, but CVSS, CWE, affected CPEs, patch status, and exploit telemetry are absent. Further analysis should start from the referenced GitHub issue and vendor release history.

Mitigation direction

  • Inventory WUZHI CMS deployments and confirm whether version 4.1.0 is present.
  • Check WUZHI CMS maintainer guidance for a fixed release or recommended workaround.
  • Apply any vendor-provided update after testing in a staging environment.
  • Restrict public access to api/sms_check.php if business use is not required.
  • Monitor web and database logs for suspicious requests to the affected endpoint.

Validation and detection

  • Confirm whether api/sms_check.php exists on deployed WUZHI CMS systems.
  • Verify the running WUZHI CMS version through trusted administrative or asset records.
  • Review access logs for requests targeting api/sms_check.php with param values.
  • Check vendor issue trackers or release notes for remediation status.
  • Perform only authorized, non-destructive validation in controlled environments.
Prepared
Confidence
medium
Sources
3

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2018-11528 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.