CVE-2025-63080 KAON CVE debrief

Who should care

Defenders and administrators responsible for KAON PG5298A and PG5298B routers should assess exposure and apply necessary mitigations. This includes verifying exposure, applying firmware updates, and monitoring for suspicious activity. Additionally, security teams and vulnerability management teams should prioritize patching and monitoring for suspicious activity.

Why it matters

CVE-2025-63080 is a high-severity vulnerability in KAON PG5298A and PG5298B routers, allowing authenticated users to perform unauthorized actions via crafted JSON-RPC requests. Defenders should prioritize verifying exposure, applying firmware updates, and monitoring for suspicious activity.

• Potential unauthorized system file reads
• Potential command execution with authenticated access
• Verification of firmware versions and JSON-RPC access controls required
• Prioritization of patching and monitoring for suspicious activity

Technical summary

The vulnerability allows authenticated users to send crafted JSON-RPC requests to KAON PG5298A and PG5298B routers, enabling operations not possible via the GUI, such as system file reads or command execution. This is due to inadequate validation of JSON-RPC requests. The vulnerability has been addressed in firmware versions 3.0.82 for PG5298A and 4.0.82 for PG5298B. Defenders should prioritize verifying exposure of KAON PG5298A and PG5298B routers, checking for firmware updates, and restricting JSON-RPC access. The vulnerability has a high CVSS score of 8.5 and is considered a high-severity vulnerability.

Defensive priority

Defenders should prioritize verifying exposure of KAON PG5298A and PG5298B routers, checking for firmware updates, and restricting JSON-RPC access.

Recommended defensive actions

• Verify exposure of KAON PG5298A and PG5298B routers in the environment
• Check for and apply firmware updates to versions 3.0.82 for PG5298A and 4.0.82 for PG5298B
• Restrict JSON-RPC access to necessary users and systems
• Monitor for suspicious JSON-RPC requests and system activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, affected products, and fixed firmware versions. The vulnerability has been publicly disclosed and verified by the CVE Program and NIST NVD. There are no known instances of exploitation, but defenders should verify exposure and apply necessary mitigations. The evidence is limited to the provided CVE record and NVD entry, and further verification is recommended.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.