# CVE-2023-38551: Cross-site scripting in Connect Secure

> An authenticated high-privileged user can inject malicious code into a victim's browser via CRLF injection, leading to cross-site scripting attacks.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-99x9-vrrc-xxw3

## What is CVE-2023-38551?

CVE-2023-38551 is a high-severity cross-site scripting vulnerability in Ivanti Connect Secure, published on 31 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A CRLF Injection vulnerability in Ivanti Connect Secure (9.x, 22.x) allows an authenticated high-privileged user to inject malicious code on a victim’s browser, thereby leading to cross-site scripting attack.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2023-38551 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38551 is a high-severity cross-site scripting vulnerability in Ivanti Connect Secure, published on 31 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38551 in the wild and no public exploit code.

Affected product: Ivanti Connect Secure. 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-38551/ (Markdown: https://insights.sbomify.com/CVE-2023-38551/index.md)
```

## Sources

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

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