# CVE-2025-3840: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

> Attackers can inject malicious scripts via the login form action parameter in the deprecated Saviynt Connect installer, potentially leading to XSS attacks.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-rx59-94qj-gp9f

## What is CVE-2025-3840?

CVE-2025-3840 is a low-severity cross-site scripting vulnerability in Saviynt OVA based Connect, published on 21 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An improper neutralization of input vulnerability was identified in the End of Life (EOL) OVA based connect installer component which is deployed for installation purposes in a customer network. This EOL component was deprecated in September 2023 with end of support extended till January 2024. An actor can manipulate the action parameter of the login form to inject malicious scripts which would lead to a XSS attack under certain conditions.

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

## Which versions are affected by CVE-2025-3840?


## How do I fix CVE-2025-3840?

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

## Is CVE-2025-3840 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3840 and fix it if it is affected.

What it is: CVE-2025-3840 is a low-severity cross-site scripting vulnerability in Saviynt OVA based Connect, published on 21 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-3840 in the wild and no public exploit code.

Affected product: Saviynt OVA based Connect. 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-2025-3840/ (Markdown: https://insights.sbomify.com/CVE-2025-3840/index.md)
```

## Sources

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

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