Jenkins Audit Trail Plugin 3.2 and earlier does not escape the error message for the URL Patterns field form validation, resulting in a reflected cross-site scripting vulnerability.
SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
The Jenkins Audit Trail Plugin (version 3.2 and earlier, from the Jenkins project) contains a flaw where the error message for the URL Patterns field's form validation is not escaped, resulting in a reflected cross-site scripting vulnerability. An attacker could exploit this by getting a user to interact with a crafted link or input that triggers the validation error, causing script to run in the victim's browser.
Heading is the official description · CVE.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from CVE.org.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
24.9 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 9 Mar 2020. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
2 related vulnerabilities in the same code over 7 months. The latest fix listed for audit-trail is 3.7.
Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.
This CVECVE-2020-2140Jenkins Audit Trail Plugin 3.2 and earlier does not escape the…9 Mar 2020
relatedHigh
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
Fixed one release later3.3 → 3.7 (org.jenkins-ci.plugins:audit-trail)
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linked
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSVSourceSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. GitHub Security Advisories and OSV.
1 package in 1 ecosystem. Main package: org.jenkins-ci.plugins:audit-trail.