# CVE-2025-54399: Memory corruption in WGR-500

> A stack-based buffer overflow in the ping command allows remote attackers to execute arbitrary code via crafted HTTP requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-2php-v593-f386

## What is CVE-2025-54399?

CVE-2025-54399 is a high-severity memory corruption vulnerability in Planet WGR-500, published on 7 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple stack-based buffer overflow vulnerabilities exist in the formPingCmd functionality of Planet WGR-500 v1.3411b190912. A specially crafted series of HTTP requests can lead to stack-based buffer overflow. An attacker can send a series of HTTP requests to trigger these vulnerabilities.This buffer overflow is related to the `ipaddr` request parameter for composing the `"ping -c <counts> <ipaddr> 2>&1 > %s &"` string.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-54399?

It affects 1 product.


Products: Planet Wgr-500 Firmware.

## How do I fix CVE-2025-54399?

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

## Is CVE-2025-54399 being exploited?

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

## Other vulnerabilities in Planet WGR-500

- [CVE-2025-48826](https://insights.sbomify.com/CVE-2025-48826/): Memory corruption in WGR-500 (high 8.8)
- [CVE-2025-54400](https://insights.sbomify.com/CVE-2025-54400/): Memory corruption in WGR-500 (high 8.8)
- [CVE-2025-54401](https://insights.sbomify.com/CVE-2025-54401/): Memory corruption in WGR-500 (high 8.8)
- [CVE-2025-54402](https://insights.sbomify.com/CVE-2025-54402/): Memory corruption in WGR-500 (high 8.8)
- [CVE-2025-54403](https://insights.sbomify.com/CVE-2025-54403/): Command injection in WGR-500 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54399 and fix it if it is affected.

What it is: CVE-2025-54399 is a high-severity memory corruption vulnerability in Planet WGR-500, published on 7 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54399 in the wild and no public exploit code.

Affected product: Planet WGR-500. 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-2025-54399/ (Markdown: https://insights.sbomify.com/CVE-2025-54399/index.md)
```

## Sources

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

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