# CVE-2024-4424: Stored XSS in CemiPark

> Attackers can inject malicious scripts into CemiPark via unvalidated input, leading to code execution in victim browsers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-33xc-pj2q-h2rm

## What is CVE-2024-4424?

CVE-2024-4424 is a medium-severity cross-site scripting vulnerability in CemiPark, published on 9 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The access control in CemiPark software does not properly validate user-entered data, which allows the stored cross-site scripting (XSS) attack. The parameters used to enter data into the system do not have appropriate validation, which makes possible to smuggle in HTML/JavaScript code. This code will be executed in the user's browser space.This issue affects CemiPark software: 4.5, 4.7, 5.03 and potentially others. The vendor refused to provide the specific range of affected products.

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

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


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

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

## Is CVE-2024-4424 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4424 is a medium-severity cross-site scripting vulnerability in CemiPark, published on 9 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-4424 in the wild and no public exploit code.

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

## Sources

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

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