CSRF vulnerability in Config File Provider Plugin

published 2019-01-09 7y ago modified 2026-06-17 4mo ago also GHSA-r5m8-5mwx-cmj8 , EUVD-2022-5101

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

A cross-site request forgery vulnerability exists in Jenkins Config File Provider Plugin 3.1 and earlier in ConfigFilesManagement.java, FolderConfigFileAction.java that allows creating and editing configuration file definitions.

Patch / fix

fixed in 1 links 1

maven org.jenkins-ci.plugins:config-file-provider 3.2

github.com/jenkinsci/config-file-provider-plugin@5c1df55 commit

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:config-file-provider	<3.2	3.2

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

github.com /jenkinsci/config-file-provider-plugin/commit/5c1df554e44b712e5d926b8d5557c592bf9f0a33
web
securityfocus.com /bid/106532
vdb-entry, web, third-party-advisory
jenkins.io /security/advisory/2018-09-25/#SECURITY-938
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000414
advisory

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.