# Jenkins subject to Cross-site Scripting

Advisory record · `GHSA-q5f8-fxrx-pw6f`

- **Identifiers:** `GHSA-q5f8-fxrx-pw6f` · `CVE-2013-0328`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 5 May 2022
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 May 2022, 02:48 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.502`; fixed in `1.502`

## 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 before 1.502 are affected by a cross-site scripting flaw. The source gives few details beyond this, and does not describe the attack vector. A remote attacker may be able to inject arbitrary web script or HTML, with unspecified vectors. Upgrade jenkins-core to version 1.502 or later.

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.013, the 70th 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-q5f8-fxrx-pw6f)

## Sources

- [GitHub Advisory Database: GHSA-q5f8-fxrx-pw6f](https://github.com/advisories/GHSA-q5f8-fxrx-pw6f)
- [OSV: GHSA-q5f8-fxrx-pw6f](https://osv.dev/vulnerability/GHSA-q5f8-fxrx-pw6f)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-0328>
- <https://access.redhat.com/security/cve/CVE-2013-0328>
- <https://bugzilla.redhat.com/show_bug.cgi?id=914876>
- <https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16>
- <http://rhn.redhat.com/errata/RHSA-2013-0638.html>
- <http://www.openwall.com/lists/oss-security/2013/02/21/7>

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-q5f8-fxrx-pw6f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q5f8-fxrx-pw6f/>. Everything for agents: <https://agentprime.io/llms.txt>.
