CVE-2015-5603 json
The HipChat for JIRA plugin before 6.30.0 for Atlassian JIRA allows remote authenticated users to execute arbitrary Java code via unspecifi…
published 2015-09-21 11 y ago modified 2026-06-17 4 mo ago also EUVD-2015-5557
- cvss
- 6.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 59.3%
- EPSS 59.3% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
The HipChat for JIRA plugin before 6.30.0 for Atlassian JIRA allows remote authenticated users to execute arbitrary Java code via unspecified vectors, related to "Velocity Template Injection Vulnerability."
Timeline
- Published
- First public exploit (Metasploit exploit/multi/http/jira_hipchat_template)
Exploit prediction
59.31% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/jira_hipchat_template Atlassian HipChat for Jira Plugin Velocity Template Injection metasploit exploit, excellent rank, 2015-10-28
- EDB-38905 Atlassian HipChat for Jira Plugin - Velocity Template Injection (Metasploit) remote, 2015-12-08
- EDB-38551 JIRA and HipChat for JIRA Plugin - Velocity Template Injection webapps, 2015-10-28
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/38905/
exploit
-
exploit-db.com
/exploits/38551/
exploit
-
confluence.atlassian.com
/jira/jira-and-hipchat-for-jira-plugin-security-advisory-2015-08-26-776650785.html
vendor-advisory
- packetstormsecurity.com /files/133401/Jira-HipChat-For-Jira-Java-Code-Execution.html
- rapid7.com /db/modules/exploit/multi/http/jira_hipchat_template
-
securityfocus.com
/archive/1/536374/100/0/threaded
mailing-list
Sources
- CVE List CVE-2015-5603
- NVD CVE-2015-5603
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.