Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2020-2230: Stored XSS in Jenkins project naming strategy description

Published Aug 12, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.4Medium · v3.1
EPSS82.7%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Jenkins
IdentifiersCVE-2020-2230CWE-79 · Improper Neutralization of Input…

Jenkins 2.251 and earlier, and Jenkins LTS 2.235.3 and earlier, contain a stored cross-site scripting vulnerability caused by improper escaping of the project naming strategy description. The vulnerable description field is rendered on the item creation page without sufficient output encoding, allowing attacker-controlled HTML or script content to be stored and later executed in other users' browsers when that UI is viewed. According to the provided context, exploitation is possible by an authenticated user with Overall/Manage permission. Jenkins 2.252 and LTS 2.235.4 fix the issue by escaping the project naming strategy description before display.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables stored XSS in the Jenkins web UI. In practice, this can allow execution of arbitrary JavaScript in the browser context of users who view the affected page, which may lead to session hijacking, CSRF-like action execution as the victim, theft of sensitive UI-accessible data, or unauthorized administrative actions depending on the victim's privileges.

Mitigation

If you can’t patch tonight, do this now.

Until patching is possible, restrict Jenkins access and configuration interfaces to trusted administrators only, minimize assignment of the Overall/Manage permission, and apply least-privilege access controls. Additional exposure reduction can be achieved through network-layer restrictions such as reverse proxy controls or IP allowlisting to limit access to the Jenkins UI.

Remediation

Patch, then assume compromise.

Upgrade Jenkins to 2.252 or later, or Jenkins LTS to 2.235.4 or later. The fixed versions properly escape the project naming strategy description before rendering it on the item creation page.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JenkinsJenkinsapplication
FAQ

Frequently asked questions

Is CVE-2020-2230 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2020-2230 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2020-2230?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2020-2230.
Is there a patch for CVE-2020-2230?
Upgrade Jenkins to 2.252 or later, or Jenkins LTS to 2.235.4 or later. The fixed versions properly escape the project naming strategy description before rendering it on the item creation page.
What products are affected by CVE-2020-2230?
Jenkins.
How severe is CVE-2020-2230?
CVE-2020-2230 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 82.7% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.