dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 28 Jul 2022.
Ucm6200 FirmwareOperating system · Grandstream

CVE-2020-5722

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-23
Fix available
A fix is available. Upgrade to 1.0.19.20 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The HTTP interface of the Grandstream UCM6200 series is vulnerable to an unauthenticated remote SQL injection via crafted HTTP request. An attacker can use this vulnerability to execute shell commands as root on versions before 1.0.19.20 or inject HTML in password recovery emails in versions before 1.0.20.17.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Grandstream UCM6200 series HTTP interface contains an unauthenticated SQL injection vulnerability allowing remote attackers to inject SQL commands via crafted HTTP requests. In versions prior to 1.0.19.20, this can be chained to achieve remote code execution as root; in versions prior to 1.0.20.17, it enables HTML injection into password recovery emails.

MitigationUpgrade the UCM6200 firmware to version 1.0.20.17 or later. If immediate upgrading is not possible, restrict network access to the HTTP management interface using firewall rules or VPN access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ucm6200 FirmwareOperating system
Affected:< 1.0.19.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device as Grandstream UCM6200
    Access the HTTP/HTTPS management interface and check the login page or device status page for the product name/model identifier. The UCM6200 series includes models UCM6202, UCM6204, UCM6208.
    Affected if The device is NOT a Grandstream UCM6200 series device (this CVE does not apply)
  2. Locate the firmware version information
    Navigate to the device web interface (usually http(s)://<device-ip>/) and look for a System Status, About, or Maintenance page that displays the firmware version. Alternatively, check the login page footer for version text.
    Affected if Unable to locate version information on the device
  3. Compare installed version against vulnerable range
    Note the firmware version displayed (format is typically 1.0.x.x) and compare numerically to 1.0.19.20. Versions below 1.0.19.20 are affected by this CVE.
    Affected if The installed firmware version is less than 1.0.19.20 (for example, 1.0.19.15, 1.0.18.5, etc.)
  4. Verify HTTP management interface is exposed
    Confirm the device HTTP/HTTPS management port (default 8089 or 443) is accessible from the network you are assessing. Test with a browser or curl request to the device IP.
    Affected if The HTTP interface is directly accessible from untrusted networks without firewall restrictions

You are affected if the device is a Grandstream UCM6200 series with firmware version below 1.0.19.20 and its HTTP management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.19.20 or later
Fixed in 1.0.19.20
Interim mitigation

Upgrade the UCM6200 firmware to version 1.0.20.17 or later. If immediate upgrading is not possible, restrict network access to the HTTP management interface using firewall rules or VPN access controls.

Recommended fix High confidence

Upgrade to UCM6200 Firmware version 1.0.20.17 or later

  1. 1. Backup the current UCM6200 configuration before performing any firmware upgrade.
  2. 2. Download the latest firmware version (1.0.20.17 or later) from the official Grandstream support website.
  3. 3. Access the UCM6200 web interface and navigate to the firmware upgrade section.
  4. 4. Upload the firmware file and initiate the upgrade process.
  5. 5. Wait for the upgrade to complete and verify the device reboots successfully.
  6. 6. Confirm the firmware version in the web interface shows 1.0.20.17 or later.
Caveat Review Grandstream release notes for any configuration or feature changes between your current version and the new version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ucm6200 Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5722 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data