Skip to main content

Planet WGR-500 CVE-2025-54399

HIGH
Stack-based Buffer Overflow (CWE-121)
2025-10-07 talos-cna@cisco.com
8.8
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach WGR-500 web interface
  2. Delivery
    Authenticate with low-privilege credentials
  3. Exploit
    Send crafted HTTP requests to formPingCmd
  4. Execution
    Overflow stack buffer via ipaddr parameter
  5. Persist
    Execute arbitrary code on router
  6. Impact
    Full device compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the Planet WGR-500 web management interface and low-privilege authenticated access (CVSS PR:L) sufficient to invoke the formPingCmd diagnostic function; the attacker must supply a crafted ipaddr parameter across a series of HTTP requests to overflow the stack buffer used to build the 'ping -c <counts> <ipaddr> 2>&1 > %s &' command string. Limiting factors: the device must expose its management interface to the attacker, valid credentials (or default/weak credentials) are needed because exploitation is not unauthenticated, and only the specific firmware build v1.3411b190912 is confirmed affected. No end-user interaction is required (UI:N).

Impact

This is a stack-based buffer overflow (CWE-121) in the formPingCmd handler of the Planet WGR-500 router, reachable over the network via a crafted series of HTTP requests against the ipaddr parameter used to build a 'ping -c <counts> <ipaddr>' command string. The provided CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8 High) indicates a network-reachable, low-complexity attack requiring low-level authentication, with full confidentiality, integrity, and availability impact - consistent with code execution on an embedded device. Publicly available exploit code exists (reported by Cisco Talos, TALOS-2025-2226), which materially raises practical risk over a theoretical finding. However, this CVE is NOT listed in CISA KEV, so there is no confirmation of active exploitation; the signals therefore point to a proven-exploitable but not-yet-widely-weaponized issue. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. The PR:L metric means an attacker needs some authenticated access to the device (consistent with a web-admin ping diagnostic feature), which tempers the raw score - this limits mass unauthenticated exploitation but is weak protection given default/weak router credentials are common. Net: a real and credible priority for anyone running this specific device, but its real-world urgency is bounded by the niche deployment footprint and the authentication prerequisite rather than by any evidence of mass exploitation.

Exploit ScenarioDerived

An attacker with access to the WGR-500 web management interface (PR:L) authenticates and submits a specially crafted series of HTTP requests to the formPingCmd endpoint, supplying an overly long or malformed ipaddr value that overflows a fixed-size stack buffer while the device composes the ping command string. Public exploit/PoC details are available via Cisco Talos (TALOS-2025-2226), lowering the bar to reliable code execution. Successful exploitation yields full compromise of the router (C:H/I:H/A:H).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Stack-based buffer overflows in the formPingCmd diagnostic handler of the Planet WGR-500 wireless router (firmware v1.3411b190912) let a network-reachable, low-privilege authenticated attacker (CVSS PR:L, UI:N) corrupt the stack by sending a crafted series of HTTP requests containing an oversized ipaddr parameter, yielding high confidentiality, integrity, and availability impact (CVSS 8.8). The flaw (CWE-121) stems from unsafe concatenation of the ipaddr value into the shell command string "ping -c <counts> <ipaddr> 2>&1 > %s &", so successful exploitation can redirect execution and potentially achieve remote code execution in the context of the router's web service. Publicly available exploit code exists (disclosed via Cisco Talos TALOS-2025-2226), though CISA KEV status is not indicated; exploitation requires the management interface to be exposed and valid credentials or default/weak credentials to reach the authenticated diagnostic function.

RemediationAI

No vendor-released patch or fixed version is identified in the available data for CVE-2025-54399, so operators must rely on compensating controls until Planet publishes updated firmware; monitor Planet's support site and the Talos advisory TALOS-2025-2226 (https://talosintelligence.com/vulnerability_reports/TALOS-2025-2226) for a fixed image. Because exploitation requires network reachability to the WGR-500 management interface plus low-privilege authenticated access, the highest-value mitigations are to remove the management interface from untrusted networks: place the router's admin UI behind a firewall/VPN or restrict access to a trusted management VLAN, and never expose it to the internet (this directly blocks the AV:N vector, though it precludes remote administration). Enforce strong, unique administrator credentials and rotate any default/weak passwords, since PR:L access is a prerequisite; this raises the bar but does not remove the underlying buffer overflow if an account is compromised. Disable or restrict remote management and the web-based diagnostic/ping feature if the firmware permits it, which removes the vulnerable formPingCmd code path at the cost of losing the built-in diagnostic tool. Additionally, segment the device so that a compromised router cannot reach other network assets, and enable logging/alerting on the device's HTTP admin endpoint to detect repeated oversized ipaddr requests. There is currently no confirmed fixed firmware version to cite, so any upgrade should be verified against Planet's advisory before being considered a durable fix.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Planet WGR-500 is a 4G LTE/DSL wireless router whose web management interface exposes a ping diagnostic routine implemented in the formPingCmd handler. The handler builds a shell command string of the form "ping -c <counts> <ipaddr> 2>&1 > %s &" without bounding the length of the attacker-supplied ipaddr request parameter, and then copies the composed string into a fixed-size stack buffer. Because the copy is unbounded, input exceeding the buffer's capacity overwrites adjacent stack memory, the classic CWE-121 stack-based buffer overflow condition. The handler is reachable over HTTP on the device's management interface, so the attack surface is the web endpoint rather than a local console; the CPE cpe:2.3:o:planet:wgr-500_firmware:1.3411b190912 confirms only the specific firmware build 1.3411b190912 is verified affected. Beyond memory corruption, the underlying construction also hints at command-injection-adjacent risk, but the reported CWE-121 class is the memory-safety defect that can be leveraged for arbitrary code execution in the web server context, typically running with elevated (root) privileges on embedded routers.

Know when Wgr 500 Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

HTTP-reachable so AV:N/AC:L; the ping diagnostic requires web-interface login so PR:L not PR:N; no user interaction and buffer overflow yields code execution giving C/I/A:H.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The Planet WGR-500 wireless router, a network edge device deployed in many small and branch environments, carries a remotely reachable memory corruption flaw in its web-based diagnostic interface that can allow an attacker with valid low-privilege credentials to seize control of the device's web service and potentially execute code. Because public exploit code is already circulating and no vendor patch has been released, every internet- or management-exposed WGR-500 in the estate should be treated as an elevated risk until it is isolated or replaced. Leadership should care because takeover of a gateway router can expose internal network traffic, enable persistent access, and turn a low-cost piece of hardware into a foothold for broader compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict the web management interface to a trusted management network or VLAN and block WAN-side access on TCP 80/443; disable remote administration where the product permits; enforce strong, unique administrative credentials and remove unused accounts; segment or isolate affected WGR-500 units from sensitive internal networks; monitor device and firewall logs for exploitation attempts; and accelerate replacement of the device if it cannot be isolated.

Threat Intelligence Overview

EPSS Score
0.8%
Top 46% exploitable
Prevalence
Low
niche SMB/VPN router model, limited enterprise and consumer footprint
Exploit
POC
Public exploit code exists
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.8%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

65
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

Affected Products (CPE)CVE.org

cpe:2.3:o:planet:wgr-500_firmware:1.3411b190912:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy