What is the CVSS score of EUVD-2025-18419?

EUVD-2025-18419 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.6%.

Which versions of Ex1200t Firmware are affected by EUVD-2025-18419?

A remote code execution vulnerability affecting TOTOLIK EX1200T routers (model 4.1.2cu.5232_B20210713) has been publicly disclosed with working exploits available.

Is there a public PoC exploit available for EUVD-2025-18419?

Yes, a public proof-of-concept exploit is available for EUVD-2025-18419. Prioritise patching immediately. EPSS: 0.6%.

How to fix or mitigate EUVD-2025-18419?

Within 24 hours: Identify and inventory all TOTOLINK EX1200T devices in your network and isolate them from critical systems. Within 7 days: Evaluate replacement options or implement compensating network controls (see below). Within 30 days: Execute migration plan to replace vulnerable devices or establish permanent network segmentation if replacement is not feasible.

Ex1200t Firmware EUVD-2025-18419

| CVE-2025-6129 HIGH

Buffer Overflow (CWE-119)

2025-06-16 cna@vuldb.com

Buffer Overflow TP-Link Ex1200t Firmware TOTOLINK

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 21:59 euvd

EUVD-2025-18419

Analysis Generated

Mar 14, 2026 - 21:59 vuln.today

PoC Detected

Jul 02, 2025 - 17:40 vuln.today

Public exploit code

CVE Published

Jun 16, 2025 - 16:15 nvd

HIGH 8.8

DescriptionCVE.org

A vulnerability classified as critical was found in TOTOLINK EX1200T 4.1.2cu.5232_B20210713. This vulnerability affects unknown code of the file /boafrm/formSaveConfig of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

AnalysisAI

Critical buffer overflow vulnerability in TOTOLINK EX1200T firmware version 4.1.2cu.5232_B20210713 affecting the HTTP POST request handler in the /boafrm/formSaveConfig endpoint. An authenticated remote attacker can exploit improper input validation on the 'submit-url' parameter to achieve arbitrary code execution with full system compromise (confidentiality, integrity, and availability impact). Public exploit code exists, increasing real-world exploitation risk.

Technical ContextAI

The vulnerability exists in the HTTP POST request handling component (specifically the formSaveConfig function) of TOTOLINK's firmware, which processes user-supplied input from the 'submit-url' parameter without adequate bounds checking. This is a classic CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) stack or heap-based buffer overflow. The affected device is a wireless router/mesh networking device (EX1200T model), and the vulnerability stems from unsafe string operations (likely strcpy, sprintf, or similar C library functions) that do not validate input length before copying to fixed-size buffers. The HTTP POST handler runs with elevated privileges as part of the router's web management interface, allowing authenticated users to write beyond allocated memory boundaries and potentially overwrite function pointers, return addresses, or other critical data structures to achieve code execution.

RemediationAI

Immediate actions: (1) Identify and inventory all TOTOLIK EX1200T devices in your environment, specifically those running firmware 4.1.2cu.5232_B20210713 or potentially earlier versions with identical vulnerable code; (2) Check TOTOLINK's official website (typically support.totolink.com or equivalent) for security patches and firmware updates; (3) If patches are available, apply them urgently via the device's web interface or firmware update mechanism, ensuring stable power and network connectivity during updates; (4) Interim mitigations if patches unavailable: (a) restrict HTTP/HTTPS access to the device's management interface to trusted IP addresses only using firewall rules or device ACLs, (b) disable remote management features if available, (c) change default/weak administrative credentials to strong, unique passwords, (d) isolate vulnerable devices on restricted VLANs with minimal trust; (5) monitor device logs for suspicious POST requests to /boafrm/formSaveConfig with unusual submit-url parameter values. Long-term: evaluate replacement with devices from vendors with more reliable security patching practices.