Jenkins Poll SCM Plugin vulnerable to Cross-Site Request Forgery

published 2017-10-04 9y ago modified 2026-06-17 4mo ago also GHSA-fv3c-6cw7-2qcq , EUVD-2022-3831

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits: 0; none known

Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it's similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.

Patch / fix

fixed in 1

maven org.jenkins-ci.plugins:pollscm 1.3.1

Is CVE-2017-1000093 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.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:pollscm	<1.3.1	1.3.1

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

jenkins.io /security/advisory/2017-07-10/
vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2017-1000093
advisory
github.com /jenkinsci/pollscm-plugin
package
jenkins.io /security/advisory/2017-07-10
web

Sources

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.