Security readout for executives and security teams
Plain-English summary
ZZCMS 8.2 has a reported SQL injection in the id parameter of adv2.php?action=modify. If a vulnerable instance is reachable and the request is accepted, database confidentiality or integrity may be at risk. The provided sources do not state authentication requirements, CVSS severity, a vendor patch, or observed exploitation.
Executive priority
Prioritize identification and containment if zzcms 8.2 is internet-facing. Business urgency is uncertain because severity, exploit activity, and patch status are not provided.
Technical view
CVE-2018-8967 describes SQL injection via the id parameter in adv2.php?action=modify in zzcms 8.2. The bundle provides a public researcher reference but no CVSS vector, CWE mapping, CPEs, patch advisory, or exploitation-in-the-wild evidence. Exposure depends on whether that route exists and is reachable in the deployed application.
Likely exposure
Likely limited to organizations running zzcms 8.2 with adv2.php present and reachable. The sources do not identify other affected versions, packaged distributions, or required privileges.
Exploitation context
The CVE and reference describe an injectable parameter, but the bundle does not show KEV status or cite active exploitation. Treat exploitation status as unconfirmed.
Researcher notes
The public record is sparse: affected product metadata is not normalized, CVSS is absent, and prerequisites are unclear. Avoid broad version claims beyond zzcms 8.2.
Mitigation direction
- Inventory any zzcms deployments and confirm whether version 8.2 is in use.
- Restrict access to administrative or content-management paths until vendor guidance is confirmed.
- Check the referenced project or vendor channels for an upgrade or fixed release.
- Review logs for unusual requests to adv2.php?action=modify.
- Apply least-privilege database permissions for the web application account.
Validation and detection
- Confirm whether adv2.php exists in deployed zzcms instances.
- Verify the deployed zzcms version against application files or release metadata.
- Check whether adv2.php?action=modify is internet-reachable or access-controlled.
- Review web and database logs around the published date and current period.
- Document whether compensating controls block untrusted access to the route.
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-2018-8967 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/Ni9htMar3/vulnerability/blob/master/zzcms_8.2/adv2.php.mdCVE 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.