# CVE-2020-25218: Auth bypass in n/a

> Attackers can bypass authentication to access the administrative web interface of Grandstream GRP261x VoIP phones.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9rcq-fc99-hxmq

## What is CVE-2020-25218?

CVE-2020-25218 is a critical authentication bypass vulnerability in n/a, published on 29 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grandstream GRP261x VoIP phone running firmware version 1.0.3.6 (Base) allow Authentication Bypass in its administrative web interface.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-25218?

It affects 7 products.


Products: Grandstream Grp2612 Firmware, Grandstream Grp2612p Firmware, Grandstream Grp2612w Firmware, Grandstream Grp2613 Firmware, Grandstream Grp2614 Firmware, Grandstream Grp2615 Firmware, Grandstream Grp2616 Firmware.

## How do I fix CVE-2020-25218?

No fix has been published for CVE-2020-25218 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25218 being exploited?

There is no known exploitation of CVE-2020-25218 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-25217](https://insights.sbomify.com/CVE-2020-25217/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25218 and fix it if it is affected.

What it is: CVE-2020-25218 is a critical authentication bypass vulnerability in n/a, published on 29 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25218 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25218/ (Markdown: https://insights.sbomify.com/CVE-2020-25218/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25218
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25218
- OSV: https://osv.dev/vulnerability/CVE-2020-25218

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25218/
Summaries are generated and may contain mistakes; the official description above is the record.