Complete lack of CSRF protection in Jenkins Selenium Plugin can lead to OS command injection

published 2020-06-03 6y ago modified 2026-06-17 4mo ago also GHSA-rp4x-xpgf-4xv7 , EUVD-2022-5205

cvss: 8.0; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Jenkins Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints, allowing attackers to perform all administrative actions provided by the plugin.

Is CVE-2020-2196 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.0	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.0	AV:N/AC:M/Au:S/C:P/I:P/A:P
GitHub	3.1	7.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:selenium	<=3.141.59	no fix listed

Affected products

Jenkins project Jenkins Selenium Plugin

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

jenkins.io /security/advisory/2020-06-03/#SECURITY-1766
web, vendor-advisory
openwall.com /lists/oss-security/2020/06/03/3
mailing-list, web, third-party-advisory
openwall.com /lists/oss-security/2022/04/14/2
mailing-list, web
nvd.nist.gov /vuln/detail/CVE-2020-2196
advisory
github.com /jenkinsci/selenium-plugin
package

Sources

CVE List CVE-2020-2196
GitHub Advisory GHSA-rp4x-xpgf-4xv7
NVD CVE-2020-2196

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.