CVE-2020-5724 in the critical feed json
The Grandstream UCM6200 series before 1.0.20.22 is vulnerable to an SQL injection via the HTTP server's websockify endpoint.
published 6y ago modified 4mo ago also EUVD-2020-26883
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.2%
- EPSS 12.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Metasploit
Summary
The Grandstream UCM6200 series before 1.0.20.22 is vulnerable to an SQL injection via the HTTP server's websockify endpoint. A remote unauthenticated attacker can invoke the challenge action with a crafted username and discover user passwords.
Patch / fix
- grandstream ucm6202_firmware 1.0.20.22
- grandstream ucm6204_firmware 1.0.20.22
- grandstream ucm6208_firmware 1.0.20.22
Is CVE-2020-5724 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 auxiliary/gather/grandstream_ucm62xx_sql_account_guess)
- Published
Exploit prediction
12.16% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/gather/grandstream_ucm62xx_sql_account_guess Grandstream UCM62xx IP PBX WebSocket Blind SQL Injection Credential Dump metasploit auxiliary, normal rank, 2020-03-30
- tenable.com https://www.tenable.com/security/research/tra-2020-17 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- n/a Grandstream UCM6200 series
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
tenable.com
/security/research/tra-2020-17
exploit, third-party-advisory
Sources
- CVE List CVE-2020-5724
- NVD CVE-2020-5724
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.