CVE-2018-6328 in the critical feed json
It was discovered that the Unitrends Backup (UB) before 10.1.0 user interface was exposed to an authentication bypass, which then could all…
published 2018-03-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18089
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 64.4%
- EPSS 64.4% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
It was discovered that the Unitrends Backup (UB) before 10.1.0 user interface was exposed to an authentication bypass, which then could allow an unauthenticated user to inject arbitrary commands into its /api/hosts parameters using backquotes.
Patch / fix
- kaseya unitrends_backup 10.1
Timeline
- First public exploit (Metasploit exploit/linux/http/ueb_api_rce)
- Published
Exploit prediction
64.37% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/http/ueb_api_rce Unitrends UEB http api remote code execution metasploit exploit, excellent rank, 2017-08-08
- EDB-45559 Unitrends UEB - HTTP API Remote Code Execution (Metasploit) remote, 2018-10-08
- EDB-44297 Unitrends UEB 10.0 - Root Remote Code Execution remote, 2018-03-16
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/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 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
exploit-db.com
/exploits/45559/
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/44297/
exploit, third-party-advisory, vdb-entry
-
support.unitrends.com
/UnitrendsBackup/s/article/000006002
vendor-advisory
-
support.unitrends.com
/UnitrendsBackup/s/article/000001150
vendor-advisory
Sources
- CVE List CVE-2018-6328
- NVD CVE-2018-6328
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.