CVE-2018-6328

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS: 65%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.2%
KEV
Not listed

Published

March 14, 2018

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated May 25, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Unitrends UEB - HTTP API Remote Code Execution (Metasploit) - Linux remote Exploit

https://www.exploit-db.com/exploits/45559/
generic🟡 PoC Available

Unitrends UEB 10.0 - Root Remote Code Execution - Linux remote Exploit

https://www.exploit-db.com/exploits/44297/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:14 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-23 01:37 UTCEG score recompute
  4. 2026-07-22 22:17 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-15 16:55 UTCEPSS rescore
  12. 2026-07-15 01:56 UTCEPSS rescore
  13. 2026-07-13 22:27 UTCEPSS rescore
  14. 2026-07-12 05:43 UTCEPSS rescore
  15. 2026-07-09 19:06 UTCEPSS rescore
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-06 16:24 UTCEPSS rescore
  18. 2026-07-05 02:27 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-28 04:53 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEPSS rescore
  24. 2026-06-27 03:06 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 31 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-18 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-16 17:50 UTCEPSS rescore
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-14 23:15 UTCEPSS rescore
  13. 2026-06-14 23:15 UTCEPSS rescore
  14. 2026-06-13 22:58 UTCEPSS rescore
  15. 2026-06-12 23:09 UTCEPSS rescore
  16. 2026-06-12 23:09 UTCEPSS rescore
  17. 2026-06-11 13:57 UTCEPSS rescore
  18. 2026-06-10 22:16 UTCEPSS rescore
  19. 2026-06-08 14:14 UTCEPSS rescore
  20. 2026-06-05 22:45 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-01 13:50 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-31 00:14 UTCEPSS rescore
  27. 2026-05-29 13:41 UTCEPSS rescore
  28. 2026-05-28 10:26 UTCEG score recompute
  29. 2026-05-28 10:26 UTCGHSA enrichment
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-25 17:46 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-45559✓ verified
    First seen Oct 8, 2018

    Unitrends UEB - HTTP API Remote Code Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-44297
    First seen Mar 16, 2018

    Unitrends UEB 10.0 - Root Remote Code Execution

    Open source ↗
  • Metasploitexploit/linux/http/ueb_api_rce✓ verified
    First seen Aug 8, 2017

    Unitrends UEB http api remote code execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-6328?
CVE-2018-6328 is a critical vulnerability published on March 14, 2018. 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.
When was CVE-2018-6328 disclosed?
CVE-2018-6328 was first published in the National Vulnerability Database on March 14, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-6328 actively exploited?
CVE-2018-6328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-6328?
CVE-2018-6328 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-6328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6328, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-6328

Explore →

Is Your Infrastructure Affected by CVE-2018-6328?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs