How severe is CVE-2013-5573?

No CVSS score has been assigned to CVE-2013-5573 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-5573?

CVE-2013-5573 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-5573?

The records we use list no patched version of org.jenkins-ci.main:jenkins-core for CVE-2013-5573. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2013-5573 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-5573 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2013-5573 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2013-5573, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-5573?

CVE-2013-5573 has an EPSS (Exploit Prediction Scoring System) score of 5.4%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-5573?

CVE-2013-5573 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-5573 published, and has it been updated?

CVE-2013-5573 was published on May 17, 2022 and was last updated on March 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-5573 — jenkins-core

CVE-2013-5573 is a Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.main:jenkins-core. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Jenkins allows Cross-Site Scripting (XSS) in User Configuration

Published

May 17, 2022

Updated

Mar 13, 2025

Affected

1 pkg

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.main:jenkins-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Cross-site scripting (XSS) vulnerability in the default markup formatter in Jenkins 1.523 allows remote attackers to inject arbitrary web script or HTML via the Description field in the user configuration.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

jenkinsjenkins

1 version

1.523

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-30408webappsphp

Jenkins 1.523 - Persistent HTML Code

by Christian Catalano · Dec 18, 2013

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.jenkins-ci.main:jenkins-core for CVE-2013-5573. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

'MyspacePolicy' permits tag("form", "action", ONSITE_OR_OFFSITE_URL, "method"); Fix 'MyspacePolicy' by restricting the policy to ONSITE_URL only or perhaps <form> could be banned entirely.

Source: Red Hat security advisory for CVE-2013-5573 (CC BY 4.0)