CVE-2019-20411Network attack vector

Wallboard settings modification via CSRF

Published Jun 29, 2020 · Updated Sep 16, 2024

Cross-site request forgery in Atlassian Jira Server before 7.13.9 and 8.0.0 through 8.4.2 allows remote attackers to modify Wallboard settings. The Wallboard endpoint accepts state-changing requests without requiring a valid CSRF token, so a forged request from an attacker-controlled page can execute with a victim's Jira session. Exploitation requires a logged-in Jira user to load the crafted page; impact is limited to unauthorized Wallboard configuration changes.

CVSS severity4.3
Medium
EPSS probability0.65%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cross-site request forgery in Atlassian Jira Server before 7.13.9 and 8.0.0 through 8.4.2 allows remote attackers to modify Wallboard settings. The Wallboard endpoint accepts state-changing requests without requiring a valid CSRF token, so a forged request from an attacker-controlled page can execute with a victim's Jira session. Exploitation requires a logged-in Jira user to load the crafted page; impact is limited to unauthorized Wallboard configuration changes.

The record

CVE
CVE-2019-20411
Published
Jun 29, 2020
Updated
Sep 16, 2024
Vendor
Atlassian
Product
Jira Server
Classifications
CWE-352, CAPEC-62, T1189
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 29, 2020CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=8.0.0 <unspecified
  2. Affected versionversion=unspecified <7.13.9
  3. Affected versionversion=unspecified <8.4.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Atlassian · Jira Serverversion=8.0.0 <unspecified; version=unspecified <7.13.9; version=unspecified <8.4.2

Published CVSS scores

4.3NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.3NVDAV:N/AC:M/Au:N/C:N/I:P/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
CAPEC-62Cross-Site Request Forgery
T1189Drive-by Compromise

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo