# CVE-2024-48569: Cross-site scripting in n/a

> Attackers can inject malicious scripts into Proactive Risk Manager forms, potentially executing code or stealing data from users.

- **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:** 30 Oct 2024
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-v4pp-cm3w-w8gh

## What is CVE-2024-48569?

CVE-2024-48569 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 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

Proactive Risk Manager version 9.1.1.0 is affected by multiple Cross-Site Scripting (XSS) vulnerabilities in the add/edit form fields, at the urls starting with the subpaths: /ar/config/configuation/ and /ar/config/risk-strategy-control/

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

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


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

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

## Is CVE-2024-48569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48569 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48569 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-2024-48569/ (Markdown: https://insights.sbomify.com/CVE-2024-48569/index.md)
```

## Sources

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

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