Skip to main content

Planet WGR-500 CVE-2025-54401

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
    Authenticate to WGR-500 web UI
  2. Delivery
    Send crafted HTTP requests to formPingCmd
  3. Exploit
    Overflow stack buffer via submit-url parameter
  4. Execution
    Execute arbitrary code on router
  5. 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 WGR-500 HTTP management interface and valid authenticated access to it (CVSS PR:L), after which the attacker sends a crafted series of HTTP requests to the formPingCmd functionality, specifically abusing the submit-url request parameter to overflow a stack buffer. Limiting factors: the attacker must hold at least low-privilege credentials (so default-credential, weak-password, or post-authentication positions are the realistic entry), and the device is a specific firmware build (v1.3411b190912); no user interaction is needed (UI:N) and complexity is low (AC:L), so once credentialed the overflow is reliably triggerable against the management interface.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates a network-reachable, low-complexity flaw requiring low-level privileges (PR:L) and no user interaction, yielding full confidentiality, integrity, and availability impact - consistent with authenticated remote code execution on a network router. Publicly available exploit code exists (referenced via the Talos report), which raises practical risk, but this is NOT the same as active exploitation: the CVE is not listed in CISA KEV and no EPSS score was provided in the input, so exploitation-in-the-wild cannot be asserted. No SSVC decision data was supplied. The key tension is that PR:L requires the attacker to already hold some authenticated access to the device's web interface, which meaningfully gates the attack despite the network vector; combined with the product's niche footprint, this reads as a genuine high-severity RCE for exposed/credentialed-adversary scenarios rather than a mass-exploitation priority. EPSS and KEV data are absent, so widespread-exploitation likelihood is unverified.

Exploit ScenarioDerived

An attacker with valid (or weak/default) credentials to the WGR-500 web management interface sends a specially crafted series of HTTP requests to the formPingCmd handler, overflowing a stack buffer via the submit-url parameter. Because public exploit/proof-of-concept detail exists through the Talos report, a credentialed or adjacent attacker could achieve arbitrary code execution on the router. The low attack complexity (AC:L) means the overflow triggers reliably once the request format is known.

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

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

Alert me

AnalysisAIv1 – Oct 08, 2026

Authenticated stack-based buffer overflow in Planet WGR-500 firmware v1.3411b190912 allows remote attackers with low-privilege credentials to achieve full compromise via crafted HTTP requests to the formPingCmd functionality, specifically the submit-url parameter. The vulnerability requires network access to the device's HTTP management interface and valid authentication (CVSS PR:L), but no user interaction, and grants high confidentiality, integrity, and availability impact. Publicly available exploit code exists, increasing the risk for unpatched devices exposed to untrusted networks.

RemediationAI

At time of analysis, no vendor-released patch has been identified. The primary recommendation is to check Planet's support site for updated firmware and apply it as soon as a patched version becomes available. Until then, restrict access to the WGR-500's HTTP management interface to trusted internal networks only, and ensure that only strong, unique credentials are used (avoid default or weak passwords) because the vulnerability requires authenticated access. Disable remote management if not required. Monitor for suspicious HTTP requests to the formPingCmd endpoint, particularly those containing unusually long or malformed submit-url parameters. These mitigations reduce the attack surface but do not eliminate the vulnerability, and they may limit administrative convenience or remote management capabilities; they should be considered temporary compensating controls until a patch is released. Refer to the Talos report at https://talosintelligence.com/vulnerability_reports/TALOS-2025-2226 for any updates.

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 wireless router whose web-based management interface includes a formPingCmd function for diagnostic ping operations. The vulnerability resides in that function, where the submit-url request parameter is copied into a fixed-length stack buffer without proper bounds checking, leading to a stack-based buffer overflow (CWE-121). An authenticated attacker can send a series of specially crafted HTTP requests to overflow the buffer, potentially corrupting adjacent stack memory and hijacking control flow to execute arbitrary code with the privileges of the web server process. The affected firmware version is 1.3411b190912, as identified by the CPE cpe:2.3:o:planet:wgr-500_firmware:1.3411b190912:*:*:*:*:*:*:*. The Talos Intelligence report TALOS-2025-2226 provides further technical details.

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

Web-reachable management endpoint (AV:N, AC:L) but the formPingCmd form requires an authenticated session, so PR:L; stack overflow enabling code execution gives full C/I/A impact.

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 submit-url request parameter.

Executive ViewAI

Why It Matters

Planet WGR-500 devices running firmware v1.3411b190912 are at risk from CVE-2025-54401, a high-severity flaw that allows an authenticated low-privilege attacker to fully compromise the device through the HTTP management interface; publicly available exploit code exists, though no vendor-released patch has been identified at time of analysis. Organizations using these devices for network routing or remote access could face data exposure, configuration tampering, and service outages, especially where management interfaces are reachable from untrusted networks. Leadership should prioritize inventorying and isolating affected devices, as exploitation requires only valid low-privilege credentials and no user interaction.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; restrict HTTP management interface to trusted networks/VPN, disable WAN/remote management, isolate affected Planet WGR-500 devices on a segmented VLAN, enforce strong low-privilege credential management, and deploy IPS/WAF rules to block formPingCmd submit-url exploitation. Consider decommissioning or replacing devices if exposure cannot be eliminated.

Threat Intelligence Overview

EPSS Score
0.7%
Top 47% exploitable
Prevalence
Low
niche SMB VPN router firmware, limited enterprise deployment 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.7%
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