CVE-2020-2230

HIGHNVD 5.48.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 83% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 5.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 147 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS PROB: 83%CVSS: 5.4Exploit: Elevated riskExposed: 147

A fix is available — apply it.

Jenkins 2.251 and earlier, LTS 2.235.3 and earlier does not escape the project naming strategy description, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by users with Overall/Manage permission.

Live · internet exposure

147 internet-exposed hosts are running an affected version of CVE-2020-2230 right now.

across 24 countries (United States, China, Germany, Japan, France)top: jenkins
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
5.4
EG Score
8.9(high)
EG Risk
78(Track)
EG Risk 78/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity89% × 45%
Exploitation83% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
83%
EPSS %ILE
100%
KEV
Not listed

Published

August 12, 2020

Last Modified

November 21, 2024

References (6)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjenkins-0:2.235.5.1600415953-1.el72020-10-22redhat
redhatopenshift4/ose-jenkins:v4.4.0-202009260441.p02020-10-13redhat
redhatjenkins-0:2.235.5.1600414805-1.el72020-09-30redhat
redhatjenkins-0:2.235.5.1600415514-1.el72020-09-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jenkins-ci.main:jenkins-core2.236 ... 2.251 (19 versions)2.252—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:51 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-23 14:15 UTCEPSS rescore
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:51 UTCEG score recompute▲ 3.50
  6. 2026-07-22 22:37 UTCEG score recompute
  7. 2026-07-22 14:05 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-19 07:22 UTCOSV refresh
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-15 16:55 UTCEPSS rescore
  13. 2026-07-15 01:57 UTCEPSS rescore
  14. 2026-07-11 08:25 UTCEPSS rescore
  15. 2026-07-11 08:25 UTCEPSS rescore
  16. 2026-07-09 19:07 UTCEPSS rescore
  17. 2026-07-04 06:29 UTCEPSS rescore
  18. 2026-07-04 06:29 UTCEPSS rescore
  19. 2026-07-01 13:46 UTCOSV refresh
  20. 2026-06-27 03:06 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-24 14:03 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 43 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-18 17:50 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-15 17:46 UTCEPSS rescore
  6. 2026-06-14 23:15 UTCEPSS rescore
  7. 2026-06-13 22:58 UTCEPSS rescore
  8. 2026-06-13 21:13 UTCOSV refresh
  9. 2026-06-12 23:10 UTCEPSS rescore
  10. 2026-06-11 13:58 UTCEPSS rescore
  11. 2026-06-10 22:16 UTCEPSS rescore
  12. 2026-06-10 13:20 UTCEPSS rescore
  13. 2026-06-08 14:15 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-07 15:23 UTCEPSS rescore
  16. 2026-06-07 15:23 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-04 13:10 UTCEPSS rescore
  24. 2026-06-04 13:10 UTCEPSS rescore
  25. 2026-06-02 20:11 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-01 13:50 UTCEPSS rescore
  28. 2026-05-31 22:29 UTCEPSS rescore
  29. 2026-05-31 22:29 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-29 13:42 UTCEPSS rescore
  33. 2026-05-28 13:43 UTCEPSS rescore
  34. 2026-05-28 13:43 UTCEPSS rescore
  35. 2026-05-27 13:39 UTCEPSS rescore
  36. 2026-05-27 13:39 UTCEPSS rescore
  37. 2026-05-27 00:23 UTCEG score recompute
  38. 2026-05-27 00:23 UTCVendor advisory
  39. 2026-05-26 13:42 UTCEPSS rescore
  40. 2026-05-26 13:42 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore
  42. 2026-05-26 07:17 UTCEPSS rescore
  43. 2026-05-24 21:42 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-49237
    First seen Dec 11, 2020

    Jenkins 2.235.3 - 'Description' Stored XSS

    Open source ↗

Frequently asked(5)

What is CVE-2020-2230?
CVE-2020-2230 is a high vulnerability published on August 12, 2020. Jenkins 2.251 and earlier, LTS 2.235.3 and earlier does not escape the project naming strategy description, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by users with Overall/Manage permission.
When was CVE-2020-2230 disclosed?
CVE-2020-2230 was first published in the National Vulnerability Database on August 12, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-2230 actively exploited?
CVE-2020-2230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2020-2230?
CVE-2020-2230 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2020-2230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-2230, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-2230

Explore →

Is Your Infrastructure Affected by CVE-2020-2230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs