Server-Side Request Forgery (SSRF) in Jenkins Confluence Publisher Plugin

published 2018-08-01 8y ago modified 2026-06-17 4mo ago also GHSA-5339-9974-hqj9 , EUVD-2022-2481

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

A server-side request forgery vulnerability exists in Jenkins Confluence Publisher Plugin 2.0.1 and earlier in ConfluenceSite.java that allows attackers to have Jenkins submit login requests to an attacker-specified Confluence server URL with attacker specified credentials.

Patch / fix

fixed in 1

maven org.jenkins-ci.plugins:confluence-publisher 2.0.2

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub	3.0	4.3	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:confluence-publisher	<2.0.2	2.0.2

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

jenkins.io /security/advisory/2018-07-30/#SECURITY-982
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1999039
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.