Planet WGR-500 CVE-2025-54399
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach WGR-500 web interface
-
DeliveryAuthenticate with low-privilege credentials
-
ExploitSend crafted HTTP requests to formPingCmd
-
ExecutionOverflow stack buffer via ipaddr parameter
-
PersistExecute arbitrary code on router
-
ImpactFull 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). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Primary rating from Vendor (cisco).
CVSS VectorVendor: cisco
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
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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
More in Wgr 500 Firmware
View allA stack-based buffer overflow in the formPingCmd handler of the Planet WGR-500 wireless router (firmware v1.3411b190912)
Command injection in the Planet WGR-500 wireless router (firmware v1.3411b190912) allows authenticated attackers to exec
OS command injection in the formPingCmd handler of Planet WGR-500 firmware v1.3411b190912 allows an authenticated remote
Authenticated OS command injection in the swctrl device-naming function of Planet WGR-500 firmware v1.3411b190912 allows
OS command injection in the swctrl functionality of Planet WGR-500 firmware build 1.3411b190912 allows a low-privileged,
Stack-based buffer overflows in the formPingCmd functionality of Planet WGR-500 firmware v1.3411b190912 allow a remote a
Authenticated stack-based buffer overflow in Planet WGR-500 firmware v1.3411b190912 allows remote attackers with low-pri
Authenticated memory corruption in Planet WGR-500 firmware 1.3411b190912 allows a low-privileged attacker with access to
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB