# CVE-2023-26987: Missing authorization in n/a

> Remote attackers can manipulate user accounts without proper authorization via crafted POST requests in Konga.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 1 May 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-3q3f-6h94-9gg7

## What is CVE-2023-26987?

CVE-2023-26987 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue discovered in Konga 0.14.9 allows remote attackers to manipulate user accounts regardless of privilege via crafted POST request.

## Which versions are affected by CVE-2023-26987?

It affects 1 product.


Products: Konga Project Konga.

## How do I fix CVE-2023-26987?

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

## Is CVE-2023-26987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42192](https://insights.sbomify.com/CVE-2021-42192/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26987 and fix it if it is affected.

What it is: CVE-2023-26987 is a medium-severity missing authorization vulnerability in n/a, published on 1 May 2023. 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-2023-26987 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-2023-26987/ (Markdown: https://insights.sbomify.com/CVE-2023-26987/index.md)
```

## Sources

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

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