# CVE-2022-38664: Cross-site Scripting in Jenkins Job Configuration History Plugin

> Attackers with job configuration permissions can inject malicious scripts via job names, leading to stored XSS in the Jenkins System Configuration History page.

- **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:** Yes
- **Published:** 23 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-28w4-h56g-grg7

## What is CVE-2022-38664?

CVE-2022-38664 is a medium-severity cross-site scripting vulnerability in Jenkins Job Configuration History Plugin, published on 23 Aug 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 Job Configuration History Plugin 1165.v8cc9fd1f4597 and earlier does not escape the job name on the System Configuration History page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure job names.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1166.vc9f255f45b |
| `org.jenkins-ci.plugins:jobConfigHistory` | Maven | All versions | 1166.vc9f255f45b |

Products: Jenkins Job Configuration History.

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

Upgrade org.jenkins-ci.plugins:jobConfigHistory to 1166.vc9f255f45b or later.

## Is CVE-2022-38664 being exploited?

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

## Other vulnerabilities in Jenkins Job Configuration History Plugin

- [CVE-2023-41933](https://insights.sbomify.com/CVE-2023-41933/): Job Configuration History Plugin's path traversal allows exploiting XXE vulnerability (high 8.8)
- [CVE-2023-41932](https://insights.sbomify.com/CVE-2023-41932/): Path traversal allows exploiting XXE vulnerability in Jenkins Job Configuration History Plugin (medium 6.5)
- [CVE-2023-41931](https://insights.sbomify.com/CVE-2023-41931/): XSS vulnerability in Jenkins Job Configuration History Plugin (medium 5.4)
- [CVE-2026-57287](https://insights.sbomify.com/CVE-2026-57287/): Jenkins Job Configuration History Plugin doesn't redact encrypted values of secrets in job and agent configurations (medium 4.3)
- [CVE-2023-41930](https://insights.sbomify.com/CVE-2023-41930/): Path traversal in Jenkins Job Configuration History Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38664 is a medium-severity cross-site scripting vulnerability in Jenkins Job Configuration History Plugin, published on 23 Aug 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-38664 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1166.vc9f255f45b
- org.jenkins-ci.plugins:jobConfigHistory (Maven): affected all versions; fixed in 1166.vc9f255f45b

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-38664/ (Markdown: https://insights.sbomify.com/CVE-2022-38664/index.md)
```

## Sources

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

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