dbcve.org
Grp2612 FirmwareOperating system · Grandstream

CVE-2020-25218

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Grandstream GRP261x VoIP phone running firmware version 1.0.3.6 (Base) allow Authentication Bypass in its administrative web interface.

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 · moderate confidence

Grandstream GRP261x VoIP phones running firmware version 1.0.3.6 contain an authentication bypass vulnerability in their web-based administrative interface, allowing remote attackers to gain unauthorized administrative access without valid credentials.

MitigationUpdate the device firmware to a patched version if available; otherwise, restrict network access to the administrative web interface using firewall rules or VLAN segmentation to limit exposure.

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
Grp2612 FirmwareOperating system
Affected:= 1.0.3.6
Grp2612p FirmwareOperating system
Affected:= 1.0.3.6
Grp2612w FirmwareOperating system
Affected:= 1.0.3.6
Grp2613 FirmwareOperating system
Affected:= 1.0.3.6
Grp2614 FirmwareOperating system
Affected:= 1.0.3.6
Grp2615 FirmwareOperating system
Affected:= 1.0.3.6
Grp2616 FirmwareOperating system
Affected:= 1.0.3.6

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 model
    Access the web administrative interface of the VoIP phone and navigate to Status or Device Info page to confirm the device is a Grandstream GRP261x series phone (2612, 2612P, 2612W, 2613, 2614, 2615, or 2616)
    Affected if The device is not a Grandstream GRP261x model
  2. Check the firmware version
    In the web interface, locate the firmware version field (typically under Status > System Info or Status > Phone Status). Confirm the exact version number displayed
    Affected if Firmware version is 1.0.3.6
  3. Verify web interface accessibility
    Attempt to access the web administrative interface via HTTP/HTTPS on the device's IP address. Confirm the login page is reachable and responds
    Affected if Web interface is exposed and accessible on the network
  4. Check authentication configuration
    In the web interface, navigate to Settings > Security or Settings > Admin Access to verify whether administrative authentication is enabled or if the authentication bypass condition exists
    Affected if Authentication can be bypassed or is not enforced on the web interface

The environment is affected if a Grandstream GRP261x phone is running firmware version 1.0.3.6 and its web administrative interface is network-accessible with an exploitable authentication bypass.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the device firmware to a patched version if available; otherwise, restrict network access to the administrative web interface using firewall rules or VLAN segmentation to limit exposure.

Recommended fix Moderate confidence

Upgrade to the latest stable firmware (e.g., version 1.0.5.7 or newer) for the GRP261x series

  1. Download the latest firmware for your specific GRP261x model from the official Grandstream support site (e.g., https://www.grandstream.com/support/firmware).
  2. Connect to the phone’s administrative web interface over HTTPS from a trusted network. If the device is currently exposed to the internet, restrict access until the upgrade is complete.
  3. Log in with an administrator account (or use the console/SSH if available).
  4. Navigate to Maintenance → Firmware Upgrade (or Settings → Device → Upgrade).
  5. Click Upload and select the downloaded firmware file. Confirm the upgrade when prompted.
  6. Allow the device to reboot; do not power off during the process.
  7. After reboot, verify the new firmware version is displayed in the web UI (e.g., Status → Device Info).
  8. Test that the administrative pages now require authentication – attempt to access a protected URL without credentials and confirm access is denied.
Caveat Brief service interruption during reboot; backup configuration before upgrading

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

Fix this in Grp2612 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25218 — 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-25218 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