A vulnerability in the Gleez CMS 1.2.0 login page could allow an unauthenticated, remote attacker to perform multiple user enumerations, which can further help an attacker to perform login attempts in excess of the configured login attempt limit. The vulnerability is due to insufficient server-side access control and login attempt limit enforcement. An attacker could exploit this vulnerability by sending modified login attempts to the Portal login page. An exploit could allow the attacker to identify existing users and perform brute-force password attacks on the Portal, as demonstrated by navigating to the user/4 URI.
CVE-2018-16703
MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence
Score 5.3 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 5.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 71.7%
- KEV
- Not listed
Published
September 7, 2018
Last Modified
November 21, 2024
References (2)
- cve@mitrehttps://github.com/gleez/cms/issues/802
- af854a3a-2127-422b-91ae-364da2661108https://github.com/gleez/cms/issues/802
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2018-16703?
CVE-2018-16703 is a medium vulnerability published on September 7, 2018. A vulnerability in the Gleez CMS 1.2.0 login page could allow an unauthenticated, remote attacker to perform multiple user enumerations, which can further help an attacker to perform login attempts in excess of the configured login attempt limit. The vulnerability is due to insufficient server-side…
When was CVE-2018-16703 disclosed?
CVE-2018-16703 was first published in the National Vulnerability Database on September 7, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-16703 actively exploited?
CVE-2018-16703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-16703?
CVE-2018-16703 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2018-16703?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16703, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-16703
Is Your Infrastructure Affected by CVE-2018-16703?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.