LiveActive security incident?Get immediate response
CVE Record

CVE-2018-17412: zzcms v8.3 contains a SQL Injection vulnerability in /user/logincheck.php via an X-Forwarded-For HTTP header.

zzcms v8.3 contains a SQL Injection vulnerability in /user/logincheck.php via an X-Forwarded-For HTTP header.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-17412 describes a SQL injection issue in zzcms v8.3. The reported problem is in the login check path and is triggered through the X-Forwarded-For HTTP header. If present in a deployed site, it may expose database-backed login logic to unauthorized manipulation.

Executive priority

Prioritize investigation if the organization runs zzcms v8.3, especially on internet-facing sites. Without evidence of active exploitation or severity scoring, urgency depends on confirmed deployment and endpoint exposure rather than the CVE record alone.

Technical view

The CVE states that zzcms v8.3 has SQL injection in /user/logincheck.php via the X-Forwarded-For header. The record does not provide CVSS, CWE, CPE, exploit details, or a named fixed version. Analysis is therefore limited to the vulnerability statement and listed public references.

Likely exposure

Exposure is most likely where zzcms v8.3 is deployed and /user/logincheck.php is reachable. The source bundle does not identify vendor CPEs, package names, hosting patterns, or affected configurations beyond the CVE description.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not state active exploitation. The issue is plausibly remotely reachable through a web login path, but the bundle does not include proof-of-concept status or observed attack evidence.

Researcher notes

The public bundle is sparse: no CVSS, CWE, CPEs, fixed version, or exploit telemetry are supplied. The strongest claim is the CVE description identifying SQL injection in /user/logincheck.php through X-Forwarded-For for zzcms v8.3.

Mitigation direction

  • Inventory any zzcms v8.3 deployments and confirm whether /user/logincheck.php is present.
  • Check upstream project or vendor guidance for a fixed release or official remediation.
  • If no fix is available, isolate, replace, or retire affected deployments.
  • Restrict access to the login endpoint where business operations permit.
  • Review trusted proxy and client IP header handling in the application stack.

Validation and detection

  • Confirm whether production or staging systems run zzcms v8.3.
  • Verify whether /user/logincheck.php is externally reachable.
  • Review application logs for abnormal login requests involving forwarded client IP headers.
  • Review code or vendor patches for parameterized database handling in logincheck.php.
  • Document compensating controls if the application cannot be patched immediately.
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-17412 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.