# CVE-2018-16704: Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users

> Logged-in users can view other users' profile pages via insecure direct object reference, exposing private user data.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hh92-wg7v-8vfr

## What is CVE-2018-16704?

CVE-2018-16704 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2018-16704?

2 open source packages ship an affected version, including gleez/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gleez/cms` | Packagist | All versions to 1.2.0 | None |
| `gleez/cms` | Packagist | All versions to 1.2.0 | None |

Products: Gleeztech Gleezcms.

## How do I fix CVE-2018-16704?

No fix has been published for CVE-2018-16704 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-16704 being exploited?

There is no known exploitation of CVE-2018-16704 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-1999021](https://insights.sbomify.com/CVE-2018-1999021/): Gleez Cms Cross-site Scripting in Profile Page (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16704 and fix it if it is affected.

What it is: CVE-2018-16704 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16704 in the wild and no public exploit code.

Affected packages and fixed versions:
- gleez/cms (Packagist): affected all versions up to 1.2.0; no fix listed
- gleez/cms (Packagist): affected all versions up to 1.2.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-16704/ (Markdown: https://insights.sbomify.com/CVE-2018-16704/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16704
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16704
- OSV: https://osv.dev/vulnerability/CVE-2018-16704

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-16704/
Summaries are generated and may contain mistakes; the official description above is the record.