# Jenkins Cross-Site Request Forgery vulnerabilities

Advisory record · `GHSA-fg4r-f9j2-36mw`

- **Identifiers:** `GHSA-fg4r-f9j2-36mw` · `CVE-2013-2034`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 17 May 2022
- **Updated:** 4 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.main:jenkins-core` (Maven): affected `<1.509.1 || >=1.513, <1.514`; fixed in `1.509.1`, `1.514`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jenkins core (org.jenkins-ci.main:jenkins-core) versions below 1.509.1, from 1.513 up to but not including 1.514, are affected by multiple cross-site request forgery vulnerabilities. A remote attacker can hijack an administrator's authentication to run arbitrary code or to deploy binaries to a Maven repository. Upgrade to version 1.509.1 or 1.514.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.016, the 76th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fg4r-f9j2-36mw)

## Sources

- [GitHub Advisory Database: GHSA-fg4r-f9j2-36mw](https://github.com/advisories/GHSA-fg4r-f9j2-36mw)
- [OSV: GHSA-fg4r-f9j2-36mw](https://osv.dev/vulnerability/GHSA-fg4r-f9j2-36mw)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-2034>
- <https://access.redhat.com/errata/RHEA-2013:1032>
- <https://access.redhat.com/security/cve/CVE-2013-2034>
- <https://bugzilla.redhat.com/show_bug.cgi?id=958958>
- <https://issues.jenkins-ci.org/browse/SECURITY-63>
- <https://issues.jenkins-ci.org/browse/SECURITY-69>
- <https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-05-02>
- <http://www.cloudbees.com/jenkins-advisory/jenkins-security-advisory-2013-05-02.cb>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fg4r-f9j2-36mw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fg4r-f9j2-36mw/>. Everything for agents: <https://agentprime.io/llms.txt>.
