# CVE-2025-63080: Authenticated RCE in KAON PG5298

> Authenticated attackers can bypass GUI restrictions via crafted JSON-RPC requests to execute commands or read files on KAON PG5298 routers.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-qr3p-6238-2p49

## What is CVE-2025-63080?

CVE-2025-63080 is a high-severity missing authorization vulnerability in KAON PG5298A, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Firmware in KAON PG5298A and PG5298B routers allow an authenticated user to send crafted JSON-RPC requests and perform operations not possible via GUI, e.g. system file read or command execution.   
This vulnerability has been fixed in firmware version: 3.0.82 for PG5298A and 4.0.82 for PG5298B.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-63080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63080 is a high-severity missing authorization vulnerability in KAON PG5298A, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63080 in the wild and no public exploit code.

Affected product: KAON PG5298A. 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-63080/ (Markdown: https://insights.sbomify.com/CVE-2025-63080/index.md)
```

## Sources

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

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