CVE-2020-2141: CSRF vulnerability in Jenkins P4 Plugin
Summary
CVE-2020-2141: CSRF vulnerability in Jenkins P4 Plugin. Affects org.jenkins-ci.plugins:p4 versions < 1.10.11. Fixed in 1.10.11. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The Jenkins P4 Plugin is a Maven-based open-source plugin that integrates Jenkins with Perforce, a version control system. It allows users to trigger builds and manage labels in Perforce directly from Jenkins. The plugin is widely used in software development and continuous integration workflows.
Vulnerability Detail
The Jenkins P4 Plugin versions 1.10.10 and earlier are affected by a cross-site request forgery (CSRF) vulnerability. This vulnerability allows attackers to perform unauthorized actions on behalf of authenticated users. Specifically, attackers can trigger builds or add labels in Perforce without the user's consent. This can lead to unauthorized code execution, data manipulation, or disruption of the CI/CD pipeline.
How To Fix
Latest published version: 1.18.1 as of 22 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.10.11
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 →
Conclusion
The CSRF vulnerability in Jenkins P4 Plugin can have serious consequences for software development and continuous integration workflows. It is crucial to upgrade to the latest version of the plugin (1.10.11 or later) to protect against unauthorized actions and ensure the integrity of the CI/CD pipeline. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:p4 →
FAQ
Cross-Site Request Forgery (CSRF) is an attack that tricks the victim into submitting a malicious request. In the case of the Jenkins P4 Plugin vulnerability, it allows attackers to perform unauthorized actions on behalf of authenticated users.
The CSRF vulnerability in Jenkins P4 Plugin can lead to unauthorized code execution, data manipulation, or disruption of the CI/CD pipeline. Attackers can trigger builds or add labels in Perforce without the user's consent.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins P4 Plugin version is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it in real-time.
No specific workaround is available for this vulnerability. It is recommended to upgrade to the latest version of the Jenkins P4 Plugin to mitigate the risk.
You can find more information about the Jenkins P4 Plugin vulnerability in the GitHub Advisory Database (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-rjjq-63c7-8724/GHSA-rjjq-63c7-8724.json).
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:p4.
