CVE Alert: CVE-2025-54402 – Planet – WGR-500

CVE-2025-54402

HIGHNo exploitation known

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` and `ipaddr` request parameters combined.

CVSS v3.1 (8.8)
AV NETWORK · AC LOW · PR LOW · UI NONE · S UNCHANGED
Vendor
Planet
Product
WGR-500
Versions
v1.3411b190912
CWE
CWE-121, CWE-121: Stack-based Buffer Overflow
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2025-10-07T13:55:10.827Z
Updated
2025-10-07T14:40:28.396Z

AI Summary Analysis

Risk verdict

High risk of remote code execution via a network-triggered stack overflow; no active exploitation indicators are present, but patching should be prioritised when feasible.

Why this matters

Successful exploitation could fully compromise the device, exposing data and disrupting network services. The flaw requires only network access and low privileges with no user interaction, enabling automated probing against exposed management interfaces.

Most likely attack path

Attacks would target the HTTP management interface over the network, sending crafted requests to trigger the overflow via the submit-url and ipaddr parameters. Preconditions are network reachability and low privileges with no user interaction, with effects limited to the device but potentially severe due to high impact on confidentiality, integrity and availability.

Who is most exposed

Edge or SMB deployments with internet-facing or poorly segmented management interfaces are most at risk.

Detection ideas

  • HTTP requests with abnormally long submit-url or ipaddr values in access logs.
  • Device crashes, kernel panics, or watchdog restarts following management traffic.
  • Unusual memory usage spikes or reboot patterns after similar requests.
  • IDS/IPS alerts for overflow-like payloads targeting the management endpoint.

Mitigation and prioritisation

  • Apply vendor patch when available; monitor related advisories.
  • If patch is unavailable, restrict management access: disable HTTP management, require VPN or dedicated mgmt VLAN, enforce TLS.
  • Implement network segmentation and firewall rules to minimise exposure.
  • Enable enhanced logging and crash diagnostics; test changes in a lab before rollout.
  • Schedule patching in a controlled maintenance window; verify device stability post-deployment.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.