CVE-2018-1000411: Jenkins JUnit Plugin CSRF vulnerability

org.jenkins-ci.plugins:junit Updated 02 Oct 2025

Summary

14/05/2022
Yes i
Moderate
6.5

CVE-2018-1000411: Jenkins JUnit Plugin CSRF vulnerability. Affects org.jenkins-ci.plugins:junit versions < 1.26. Fixed in 1.26. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Jenkins JUnit Plugin is a Maven ecosystem package that provides support for JUnit test result reporting in Jenkins. It allows users to view and analyze test results within the Jenkins environment. The plugin is widely used in software development and continuous integration workflows.

Vulnerability Detail

The JUnit Plugin version 1.25 and earlier are affected by a cross-site request forgery (CSRF) vulnerability. This vulnerability exists in the TestObject.java file, allowing an attacker to set the description of a test result. An attacker could exploit this vulnerability to manipulate test results, potentially leading to false reports and misleading analysis. The vulnerability has a CVSS score of 6.5, indicating a moderate severity level.

How To Fix

Latest published version: 1442.vb_b_a_467df2767 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.26

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the JUnit Plugin to mitigate the CSRF vulnerability.

Conclusion

The Jenkins JUnit Plugin version 1.25 and earlier are vulnerable to a CSRF attack that allows manipulation of test results. To mitigate this vulnerability, it is crucial to update the plugin to version 1.26 or later. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:junit →

Share this vulnerability

FAQ

This vulnerability allows an attacker to manipulate test results in Jenkins, potentially leading to false reports and misleading analysis.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using just the pom.xml file.

Yes, upgrading the JUnit Plugin to version 1.26 or later fixes the CSRF vulnerability.

No, there is no known workaround for this vulnerability. It is crucial to update to the fixed version of the JUnit Plugin.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:junit.

How To Fix

Latest published version: 1442.vb_b_a_467df2767 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.26

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback