# CVE-2018-16703: Information disclosure in n/a

> Unauthenticated attackers can enumerate users and bypass login attempt limits in Gleez CMS, facilitating brute-force attacks.

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

## What is CVE-2018-16703?

CVE-2018-16703 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-521 (Weak Password Requirements), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Gleeztech Gleez Cms.

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

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

## Is CVE-2018-16703 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13340](https://insights.sbomify.com/CVE-2018-13340/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16703 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16703 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-16703/ (Markdown: https://insights.sbomify.com/CVE-2018-16703/index.md)
```

## Sources

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

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