# CVE-2012-6074: Jenkins allows Cross-Site Scripting (XSS)

> Authenticated users with write access can inject arbitrary scripts into Jenkins, potentially leading to code execution or account takeover.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/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:** 24 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9hr6-5x6g-gg5g

## What is CVE-2012-6074?

CVE-2012-6074 is a low-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 24 Feb 2013. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in Jenkins before 1.491, Jenkins LTS before 1.480.1, and Jenkins Enterprise 1.424.x before 1.424.6.13, 1.447.x before 1.447.4.1, and 1.466.x before 1.466.10.1 allows remote authenticated users with write access to inject arbitrary web script or HTML via unspecified vectors.

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

## Which versions are affected by CVE-2012-6074?

4 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 1.480.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | All versions | 1.480.1 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 1.481 | 1.491 |
| `org.jenkins-ci.main:jenkins-core` | Maven | From 1.481 | 1.491 |

Products: Cloudbees Jenkins, Jenkins Jenkins.

## How do I fix CVE-2012-6074?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 1.480.1 or 1.491.

## Is CVE-2012-6074 being exploited?

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

## Other vulnerabilities in Jenkins Jenkins

- [CVE-2012-0785](https://insights.sbomify.com/CVE-2012-0785/): Hash collision attack vulnerability in Jenkins (high 7.5)
- [CVE-2013-2034](https://insights.sbomify.com/CVE-2013-2034/): Jenkins Cross-Site Request Forgery vulnerabilities (medium 6.8)
- [CVE-2012-6073](https://insights.sbomify.com/CVE-2012-6073/): Jenkins affected by Open Redirect Vulnerability (medium 5.8)
- [CVE-2012-6072](https://insights.sbomify.com/CVE-2012-6072/): Jenkins allows HTTP Injection and Response Splitting (medium 4.3)
- [CVE-2012-0324](https://insights.sbomify.com/CVE-2012-0324/): Jenkins allows Cross-Site Scripting (XSS) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6074 and fix it if it is affected.

What it is: CVE-2012-6074 is a low-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 24 Feb 2013. 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-2012-6074 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 1.480.1
- org.jenkins-ci.main:jenkins-core (Maven): affected all versions; fixed in 1.480.1
- org.jenkins-ci.main:jenkins-core (Maven): affected from 1.481; fixed in 1.491
- org.jenkins-ci.main:jenkins-core (Maven): affected from 1.481; fixed in 1.491

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

## Sources

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

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