# CVE-2019-11393: Privilege escalation in n/a

> Unprivileged users can escalate to administrator privileges in M/Monit by manipulating the admin parameter during a password change request.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-45fw-396c-r96x

## What is CVE-2019-11393?

CVE-2019-11393 is a critical vulnerability in n/a, published on 21 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in /admin/users/update in M/Monit before 3.7.3. It allows unprivileged users to escalate their privileges to an administrator by requesting a password change and specifying the admin parameter.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2019-11393?

It affects 1 product.


Products: Tildeslash Monit.

## How do I fix CVE-2019-11393?

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

## Is CVE-2019-11393 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1898](https://insights.sbomify.com/CVE-2004-1898/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-1083](https://insights.sbomify.com/CVE-2003-1083/): Memory corruption in n/a (critical 10.0)
- [CVE-2022-26563](https://insights.sbomify.com/CVE-2022-26563/): Auth bypass in n/a (high 8.8)
- [CVE-2004-1899](https://insights.sbomify.com/CVE-2004-1899/): Memory corruption in n/a (medium 5.0)
- [CVE-2003-1084](https://insights.sbomify.com/CVE-2003-1084/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11393 and fix it if it is affected.

What it is: CVE-2019-11393 is a critical vulnerability in n/a, published on 21 Apr 2019. 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-2019-11393 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-2019-11393/ (Markdown: https://insights.sbomify.com/CVE-2019-11393/index.md)
```

## Sources

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

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