Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users

published 2018-09-07 8y ago modified 2026-06-17 4mo ago also GHSA-hh92-wg7v-8vfr , EUVD-2022-4153

cvss: 4.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

An issue was discovered in Gleez CMS v1.2.0. Because of an Insecure Direct Object Reference vulnerability, it is possible for attackers (logged in users) to view profile page of other users, as demonstrated by navigating to user/3 on demo.gleezcms.org.

Is CVE-2018-16704 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub	3.0	4.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	gleez/cms	<=1.2.0	no fix listed

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

github.com /gleez/cms/issues/801
web, mitigation, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-16704
advisory
github.com /gleez/cms
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.