# CVE-2024-34243: Konga is vulnerable to Cross Site Scripting (XSS) attacks

> An attacker can execute arbitrary scripts in the Konga admin dashboard via the username parameter, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-93pf-mrc8-4g3h

## What is CVE-2024-34243?

CVE-2024-34243 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Konga v0.14.9 is vulnerable to Cross Site Scripting (XSS) via the username parameter.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-34243?

2 open source packages ship an affected version, including kongadmin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kongadmin` | npm | All versions to 0.14.9 | None |
| `kongadmin` | npm | All versions to 0.14.9 | None |

Products: Pantsel Konga.

## How do I fix CVE-2024-34243?

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

## Is CVE-2024-34243 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-39846](https://insights.sbomify.com/CVE-2023-39846/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34243 and fix it if it is affected.

What it is: CVE-2024-34243 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-34243 in the wild and no public exploit code.

Affected packages and fixed versions:
- kongadmin (npm): affected all versions up to 0.14.9; no fix listed
- kongadmin (npm): affected all versions up to 0.14.9; no fix listed

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

## Sources

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

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