The JMX monitoring flag in Atlassian Jira Server and Data Center before version 8.6.0 allows remote attackers to turn the JMX monitoring fl…

published 2020-02-06 6y ago modified 2026-06-17 4mo ago also EUVD-2019-10954

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

The JMX monitoring flag in Atlassian Jira Server and Data Center before version 8.6.0 allows remote attackers to turn the JMX monitoring flag off or on via a Cross-site request forgery (CSRF) vulnerability.

Patch / fix

fixed in 1

Atlassian Jira Server 8.6.0

Is CVE-2019-20405 in your stack? 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.55% chance of exploitation in the next 30 days, higher than 46% 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:N/UI:R/S:U/C:N/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Atlassian Jira Server

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

jira.atlassian.com /browse/JRASERVER-70570
issue-tracking, vendor-advisory

Sources

CVE List CVE-2019-20405
NVD CVE-2019-20405

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.