# CVE-2025-56498: Command injection in n/a

> An authenticated attacker can inject arbitrary system commands via the ping6 interface, leading to full system compromise with root privileges.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-crh3-pqq2-w5xm

## What is CVE-2025-56498?

CVE-2025-56498 is a medium-severity command injection vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An OS command injection vulnerability exists in PLDT WiFi Router's Prolink PGN6401V Firmware 8.1.2 web management interface. The ping6.asp page submits user input to the /boaform/formPing6 endpoint via the pingAddr parameter, which is not properly sanitized. An authenticated attacker can exploit this flaw by injecting arbitrary system commands, which are executed by the underlying operating system with root privileges. The router uses the Boa web server (version 0.93.15) to handle the request. Successful exploitation can lead to full system compromise and unauthorized control of the network device.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Prolink2u Pgn6401v Firmware.

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

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

## Is CVE-2025-56498 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56498 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56498 is a medium-severity command injection vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56498 exists.

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-2025-56498/ (Markdown: https://insights.sbomify.com/CVE-2025-56498/index.md)
```

## Sources

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

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