# CVE-2022-41240: Stored XSS vulnerability in Jenkins Walti plugin

> Attackers can inject malicious scripts via Walti API responses, potentially compromising Jenkins users and 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:** 21 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-7qpm-vmwv-hq7h

## What is CVE-2022-41240?

CVE-2022-41240 is a medium-severity cross-site scripting vulnerability in Jenkins Walti Plugin, published on 21 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jenkins Walti Plugin 1.0.1 and earlier does not escape the information provided by the Walti API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide malicious API responses from Walti.

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

## Which versions are affected by CVE-2022-41240?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:walti. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:walti` | Maven | All versions to 1.0.1 | None |
| `org.jenkins-ci.plugins:walti` | Maven | All versions to 1.0.1 | None |

Products: Jenkins Walti.

## How do I fix CVE-2022-41240?

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

## Is CVE-2022-41240 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41240 and fix it if it is affected.

What it is: CVE-2022-41240 is a medium-severity cross-site scripting vulnerability in Jenkins Walti Plugin, published on 21 Sep 2022. 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-2022-41240 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:walti (Maven): affected all versions up to 1.0.1; no fix listed
- org.jenkins-ci.plugins:walti (Maven): affected all versions up to 1.0.1; 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-2022-41240/ (Markdown: https://insights.sbomify.com/CVE-2022-41240/index.md)
```

## Sources

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

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