# CVE-2018-19437: Auth bypass in n/a

> Remote authenticated users can change the administrator password due to insecure cookie handling, leading to privilege escalation and account takeover.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-298v-7gc3-86vj

## What is CVE-2018-19437?

CVE-2018-19437 is a high-severity authentication bypass vulnerability in n/a, published on 22 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UCMS 1.4.7 allows remote authenticated users to change the administrator password because $_COOKIE['admin_'.cookiehash] is used for arbitrary cookie values that are set and not empty.

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

It affects 1 product.


Products: Ucms Project Ucms.

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

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

## Is CVE-2018-19437 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38297](https://insights.sbomify.com/CVE-2022-38297/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-35426](https://insights.sbomify.com/CVE-2022-35426/): File upload in n/a (critical 9.8)
- [CVE-2020-25537](https://insights.sbomify.com/CVE-2020-25537/): File upload in n/a (critical 9.8)
- [CVE-2020-25483](https://insights.sbomify.com/CVE-2020-25483/): File upload in n/a (critical 9.8)
- [CVE-2018-17035](https://insights.sbomify.com/CVE-2018-17035/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19437 is a high-severity authentication bypass vulnerability in n/a, published on 22 Nov 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-19437 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-19437/ (Markdown: https://insights.sbomify.com/CVE-2018-19437/index.md)
```

## Sources

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

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