Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-54401: CWE-121: Stack-based Buffer Overflow in Planet WGR-500

0
High
VulnerabilityCVE-2025-54401cvecve-2025-54401cwe-121
Published: Tue Oct 07 2025 (10/07/2025, 13:55:10 UTC)
Source: CVE Database V5
Vendor/Project: Planet
Product: WGR-500

Description

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.

AI-Powered Analysis

AILast updated: 10/07/2025, 15:01:42 UTC

Technical Analysis

CVE-2025-54401 identifies a stack-based buffer overflow vulnerability in the Planet WGR-500 router firmware version v1.3411b190912. The vulnerability resides in the formPingCmd functionality, which processes HTTP requests containing the 'submit-url' parameter. By sending a carefully crafted sequence of HTTP requests, an attacker can overflow a stack buffer, potentially overwriting return addresses or control data on the stack. This can lead to arbitrary code execution with the privileges of the affected process, which typically runs with elevated rights on the router. The vulnerability requires the attacker to have network access and low privileges (PR:L), but does not require user interaction (UI:N). The CVSS v3.1 score of 8.8 reflects the ease of exploitation (low attack complexity), the network attack vector, and the high impact on confidentiality, integrity, and availability. While no public exploits are currently known, the nature of stack-based buffer overflows makes this a critical concern, as successful exploitation could allow attackers to take full control of the device, intercept or manipulate network traffic, or disrupt network services. The lack of available patches at the time of publication increases the urgency for mitigation. The vulnerability is classified under CWE-121, a common and well-understood category of memory corruption bugs that have historically led to severe security breaches.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on Planet WGR-500 routers in their network infrastructure. Successful exploitation could lead to unauthorized remote code execution, allowing attackers to gain control over the router. This compromises the confidentiality of network traffic passing through the device, potentially exposing sensitive data. Integrity can be undermined by attackers manipulating routing or firewall rules, enabling man-in-the-middle attacks or injecting malicious payloads. Availability is also at risk, as attackers could disrupt network connectivity by crashing or disabling the device. Critical sectors such as finance, healthcare, government, and telecommunications that depend on stable and secure network equipment may face operational disruptions, data breaches, or espionage. The vulnerability’s network-based attack vector means that attackers do not need physical access, increasing the threat surface. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for rapid weaponization once details become widely known.

Mitigation Recommendations

1. Immediate mitigation involves restricting network access to the management interface of the Planet WGR-500 routers, ideally limiting it to trusted internal networks or VPN connections. 2. Employ network segmentation to isolate vulnerable devices from critical infrastructure and sensitive data flows. 3. Monitor network traffic for unusual HTTP requests targeting the formPingCmd functionality or anomalous patterns indicative of exploitation attempts. 4. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics capable of detecting buffer overflow attempts against this device. 5. Coordinate with the vendor to obtain and apply firmware updates or patches as soon as they become available. 6. If patches are delayed, consider temporary device replacement or disabling vulnerable services where feasible. 7. Conduct regular security audits and vulnerability assessments on network devices to identify and remediate similar issues proactively. 8. Educate network administrators about this vulnerability and ensure incident response plans include scenarios involving router compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
talos
Date Reserved
2025-07-21T21:08:33.897Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68e52784a677756fc992c204

Added to database: 10/7/2025, 2:45:24 PM

Last enriched: 10/7/2025, 3:01:42 PM

Last updated: 10/9/2025, 4:12:46 PM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats