CVE-2019-11580 kev+ ransomware in the critical feed json
Atlassian Crowd and Crowd Data Center had the pdkinstall development plugin incorrectly enabled in release builds.
published 7y ago modified 4mo ago also EUVD-2019-3250
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Exploited
- added 2021-11-03, used in ransomware
- epss
- 95.4%
- EPSS 95.4% chance of exploitation in 30 days, percentile 99.8%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
Atlassian Crowd and Crowd Data Center had the pdkinstall development plugin incorrectly enabled in release builds. Attackers who can send unauthenticated or authenticated requests to a Crowd or Crowd Data Center instance can exploit this vulnerability to install arbitrary plugins, which permits remote code execution on systems running a vulnerable version of Crowd or Crowd Data Center. All versions of Crowd from version 2.1.0 before 3.0.5 (the fixed version for 3.0.x), from version 3.1.0 before 3.1.6 (the fixed version for 3.1.x), from version 3.2.0 before 3.2.8 (the fixed version for 3.2.x), from version 3.3.0 before 3.3.5 (the fixed version for 3.3.x), and from version 3.4.0 before 3.4.4 (the fixed version for 3.4.x) are affected by this vulnerability.
Patch / fix
cisa required action Apply updates per vendor instructions.
- Atlassian Crowd 3.0.5, 3.1.6, 3.2.8, 3.3.5, 3.4.4
Is CVE-2019-11580 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 FencerTimeline
- First public exploit (Metasploit exploit/multi/http/atlassian_crowd_pdkinstall_plugin_upload_rce)
- Published
- Added to CISA KEV
- CISA patch deadline
- CISA SSVC: exploitation active
Known exploited
- Added
- 5y ago
- Patch by
- 2022-05-03 (4y ago)
- Ransomware
- Known to be used in ransomware campaigns
- Required action
- Apply updates per vendor instructions.
- Vendor, product
- Atlassian, Crowd and Crowd Data Center
- CISA name
- Atlassian Crowd and Crowd Data Center Remote Code Execution Vulnerability
ATT&CK techniques
How it is exploited and what it leads to, in MITRE ATT&CK terms.
- T1059 Command and Scripting Interpreter primary impact
kev release 2025-07-28, att&ck v16.1. KEV to ATT&CK mappings by the MITRE Center for Threat-Informed Defense (Mappings Explorer, Apache-2.0). © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. Terms of use
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
95.36% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/atlassian_crowd_pdkinstall_plugin_upload_rce Atlassian Crowd pdkinstall Unauthenticated Plugin Upload RCE metasploit exploit, excellent rank, 2019-05-22
- Nuclei template Atlassian Crowd and Crowd Data Center - Unauthenticated Remote Code Execution nuclei detection template
- packetstormsecurity.com http://packetstormsecurity.com/files/163810/Atlassian-Crowd-pdkinstall-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Atlassian Crowd
References
-
packetstormsecurity.com
/files/163810/Atlassian-Crowd-pdkinstall-Remote-Code-Execution.html
exploit, third-party-advisory, vdb-entry
-
jira.atlassian.com
/browse/CWD-5388
issue-tracking, mitigation, vendor-advisory
-
securityfocus.com
/bid/108637
vdb-entry, broken-link
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-11580
government-resource, us-government-resource
Sources
- CVE List CVE-2019-11580
- NVD CVE-2019-11580
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.