# CVE-2021-42192: Privilege escalation in n/a

> An attacker can escalate privileges in Konga via a specially crafted request due to incorrect access control.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 4 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** CVE-2021-44103, GHSA-g934-4c2x-9pcq

## What is CVE-2021-42192?

CVE-2021-42192 is a high-severity vulnerability in n/a, published on 4 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Konga v0.14.9 is affected by an incorrect access control vulnerability where a specially crafted request can lead to privilege escalation.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-42192?

It affects 1 product.


Products: Konga Project Konga.

## How do I fix CVE-2021-42192?

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

## Is CVE-2021-42192 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-42192 exists.

Public exploit code:

- KONGA 0.14.9 - Privilege Escalation (nuclei): http/cves/2021/CVE-2021-42192.yaml

## Other vulnerabilities in n/a

- [CVE-2023-26987](https://insights.sbomify.com/CVE-2023-26987/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42192 and fix it if it is affected.

What it is: CVE-2021-42192 is a high-severity vulnerability in n/a, published on 4 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-42192 exists.

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

## Sources

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

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