CVE-2020-2184: CSRF vulnerability in Jenkins CVS Plugin

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

Summary

24/05/2022
Yes i
Moderate
4.3

CVE-2020-2184: CSRF vulnerability in Jenkins CVS Plugin. Affects org.jenkins-ci.plugins:cvs versions < 2.16. Fixed in 2.16. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins CVS Plugin is a Maven-based package that provides integration with the CVS version control system. It allows users to connect to CVS repositories, manage tags, and perform various CVS operations within the Jenkins environment.

Vulnerability Detail

The CVS Plugin version 2.15 and earlier suffer from a cross-site request forgery (CSRF) vulnerability. These versions do not require POST requests for several HTTP endpoints, enabling attackers to exploit CSRF vulnerabilities. This allows them to create and manipulate tags and connect to URLs specified by the attacker. The vulnerability has been assigned a CVSSv3 score of 4.3 (Medium severity).

How To Fix

Latest published version: 502.v02d5a_0c6b_9a_3 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

2.16

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 specific workaround provided for this vulnerability. Upgrading to the fixed version is the recommended solution.

Conclusion

The Jenkins CVS Plugin version 2.15 and earlier are vulnerable to a CSRF vulnerability that allows unauthorized actions within the plugin. Upgrading to version 2.16 or later is recommended to mitigate this vulnerability. For additional support, please contact DevNack.com.

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

Share this vulnerability

FAQ

The vulnerability allows attackers to perform unauthorized actions, such as creating and manipulating tags, within the Jenkins CVS Plugin. It can also be used to connect to arbitrary URLs specified by the attacker.

You can use the Vulert Playground (https://vulert.com/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.

The CVSSv3 score for this vulnerability is 4.3, indicating a medium severity level.

There are no known public exploits available for this vulnerability at the time of this report.

For further support on vulnerability remediation, you can contact info@devnack.com.

Related vulnerabilities

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

How To Fix

Latest published version: 502.v02d5a_0c6b_9a_3 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

2.16

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