Jenkins Files Found Trigger Plugin allows attackers to check for existence of attacker-specified file path on Jenkins controller file system

published 2022-07-27 4y ago modified 2026-06-17 4mo ago also GHSA-jj8j-6jq7-gmvh , EUVD-2022-6362

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

Jenkins Files Found Trigger Plugin 1.5 and earlier does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

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

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:files-found-trigger	<=1.5	no fix listed

Affected products

Jenkins project Jenkins Files Found Trigger Plugin

Classification

Weakness

CWE-862 Missing Authorization

References

jenkins.io /security/advisory/2022-07-27/#SECURITY-2210
web, vendor-advisory
openwall.com /lists/oss-security/2022/07/27/1
mailing-list, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2022-36914
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.