CVE Alert: CVE-2025-9780 – TOTOLINK – A702R

CVE-2025-9780

HIGHNo exploitation known

A flaw has been found in TOTOLINK A702R 4.0.0-B20211108.1423. Affected by this issue is the function sub_419BE0 of the file /boafrm/formIpQoS. This manipulation of the argument mac causes buffer overflow. The attack can be initiated remotely. The exploit has been published and may be used.

CVSS v3.1 (8.8)
Vendor
TOTOLINK
Product
A702R
Versions
4.0.0-B20211108.1423
CWE
CWE-120, Buffer Overflow
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Published
2025-09-01T13:02:08.548Z
Updated
2025-09-01T13:02:08.548Z

AI Summary Analysis

Risk verdict

High risk: a network-accessible buffer overflow in a router-type device has public PoC and exploit activity; treat as urgent given remote code execution potential.

Why this matters

An attacker can gain full control of the device without user interaction, enabling traffic interception, modification or service disruption. Public PoC increases opportunistic exploitation, potentially enabling broader network compromise or pivot to connected systems.

Most likely attack path

Attackers exploit over the network with low required privileges; no user interaction needed. Successful exploitation yields code execution and full device compromise, with the potential to influence routing, monitoring or firewall rules, possibly exposing further hosts in the network.

Who is most exposed

Devices deployed in networks with exposed management interfaces (e.g., consumer/SME routers) that run older firmware and are reachable from untrusted networks are most at risk; systems lacking timely patching or compensating controls are particularly vulnerable.

Detection ideas

  • Repeated attempts to access management endpoints from external networks.
  • Unauthorised crashes or unexpected reboots of the device.
  • Logs showing memory corruption events or abnormal process behaviour.
  • Sudden changes to routing rules or traffic paths.
  • Known PoC/exploit patterns or anomalies flagged by IDS/IPS on access to the management surface.

Mitigation and prioritisation

  • Apply vendor firmware update that addresses the flaw; verify success before returning devices to production.
  • If patching is delayed, disable or limit WAN/remote management access; restrict to trusted networks and VPNs.
  • Implement strict network segmentation and monitor management interfaces for anomalies.
  • Validate backup and recovery plans; prepare a rollback for failed patches.
  • If KEV is confirmed or EPSS ≥ 0.5, treat as priority 1; otherwise maintain high-priority remediation and continuous monitoring.

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.