Vulnerability in Gleez CMS (CVE-2018-13340)
Summary
Vulnerability in Gleez CMS (CVE-2018-13340). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Gleez CMS 1.2.0 has CSRF, as demonstrated by a /page/add request.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2018-13340 was discovered in Gleez CMS.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Gleez CMS CVE-2018-13340".
CVE-2018-13340 (Gleez CMS). Severity: Info.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2018-13340) in Gleez CMS. A serious software flaw has been identified.
Target versions of Gleez CMS (see vendor advisory). If running in production, identify exposure immediately.
Severity: Info. Low severity or not yet rated.
Update to the patched release as listed in the vendor advisory.
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- report github.com