JunitApplication · Jenkins
CVE-2023-25761
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins JUnit Plugin 1166.va_436e268e972 and earlier does not escape test case class names in JavaScript expressions, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control test case class names in the JUnit resources processed by the plugin.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins JUnit Plugin fails to escape test case class names when rendering them in JavaScript expressions, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers who can control test case class names in JUnit XML files processed by the plugin can inject malicious JavaScript that executes in the browsers of users viewing test result reports.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JunitApplication
<= 1166.va_436e268e972CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check JUnit Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed and locate the JUnit plugin in the list, or use the Jenkins CLI to query the plugin versionAffected if The installed version is 1166 or any version with the suffix va_436e268e972 (i.e., <= 1166.va_436e268e972)
-
Identify JUnit XML report publishing configurationReview job configurations to determine if a 'Publish JUnit test result report' post-build step is configured with an XML file path patternAffected if Jobs are configured to publish JUnit test results from XML files
-
Verify test result reports are accessible in UIAccess the test result report pages in Jenkins (typically at /job/[job-name]/[build-number]/testReport/) to confirm reports are being generated and renderedAffected if Test result reports are being generated and can be viewed in the Jenkins web interface
-
Inspect test report content for class namesView individual test case details in the JUnit test report UI and examine the 'Class' or 'Class Name' field displayed on the pageAffected if Test case class names are rendered in the browser without visible encoding/escaping (view page source to check for unescaped characters like < > or quotes)
-
Review recent JUnit XML importsCheck the Jenkins build logs for entries indicating JUnit test result publishing (search for 'JUnit' or 'Publishing JUnit test result report')Affected if JUnit XML reports have been processed and published to Jenkins recently
The environment is affected if the JUnit Plugin version is 1166 or lower AND JUnit test result reports are being published and viewed in the Jenkins web interface, as this provides the JavaScript context where unsanitized class names would be rendered.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Jenkins JUnit Plugin to version 1167 or later which implements proper escaping of test case class names in JavaScript contexts.
JUnit Plugin version > 1166.va_436e268e972 (latest stable release)
- 1. Navigate to Manage Jenkins > Manage Plugins
- 2. Go to the 'Installed' tab and locate the 'JUnit Plugin'
- 3. Check the current installed version (ensure it is higher than 1166.va_436e268e972)
- 4. If not upgraded, go to the 'Available' tab and install the latest version of the JUnit Plugin
- 5. Restart Jenkins if required to complete the installation
- 6. Verify the upgrade was successful by checking the plugin version again
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Junit
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25761 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data