basicsecurity.net
Proof, not just disclosure.
Threats / Grandstream / CVE-2020-5722
CVE-2020-5722 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Grandstream UCM6200 vulnerability

Grandstream UCM6200 series contains an unauthenticated SQL injection vulnerability allowing remote code execution with root privileges via crafted HTTP requests.

Verdict

Today item — known-exploited.

An unauthenticated remote attacker can exploit SQL injection in the UCM6200 to execute arbitrary code with root-level privileges. The high EPSS score and confirmed wild exploitation indicate active threat activity against this unified communications platform.

CISA KEV Yes · 2022-01-283EPSS 0.84047 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
26 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-01-28).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.84047 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Grandstream, UCM6200. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-89 · SQL InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTTP request containing SQL injection payload targeting the UCM6200 application.
Business
The organization's voice and communications infrastructure becomes directly accessible to unauthenticated attackers without requiring valid credentials.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary SQL commands to extract sensitive data or modify application logic within the database.
Business
Call records, user credentials, configuration data, and communication logs are exposed or corrupted, compromising confidentiality and integrity.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage the SQL injection to achieve remote code execution with root-level system privileges on the UCM6200 server.
Business
The attacker gains complete control of the communications platform, enabling persistent access, lateral movement, and potential compromise of connected systems.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 26 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by tenable (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by tenableCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.