CVE-2025-29651: Unauthenticated SQL Injection Vulnerability in TP-LINK M7650 Router

Overview

An SQL Injection vulnerability has been identified in the TP-Link M7650 4G LTE Mobile Wi-Fi Router’s firmware, posing a severe threat to the security and integrity of data in systems utilizing this router. Specific to firmware version 1.0.7 Build 170623 Rel.1022n, the vulnerability allows an unauthenticated attacker to inject malicious SQL statements into the username and password fields, potentially compromising the system or leading to data leakage. This blog post provides a detailed technical analysis of this vulnerability, its potential impact, and recommended mitigation strategies.

Vulnerability Summary

CVE ID: CVE-2025-29651
Severity: Critical (9.8 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise, potential data leakage

Affected Products

Product | Affected Versions

TP-Link M7650 4G LTE Mobile Wi-Fi Router | Firmware Version: 1.0.7 Build 170623 Rel.1022n

How the Exploit Works

The vulnerability arises due to the router firmware’s inadequate sanitization of user input in the username and password fields. An attacker can exploit this flaw by injecting malicious SQL commands into these fields, manipulating the system’s database queries. As a result, this could allow the attacker to bypass authentication, alter, or extract sensitive data from the database, or even execute arbitrary commands on the server.

Conceptual Example Code

Here’s a conceptual example of how an attacker might exploit this vulnerability:

POST /login HTTP/1.1
Host: router.example.com
Content-Type: application/x-www-form-urlencoded
username=admin'; DROP TABLE users; --&password=pass

In this example, the attacker attempts to log in with a specially crafted username. The SQL statement in the username field (i.e., `admin’; DROP TABLE users; –`) is designed to end the original SQL query (`admin’`) and start a new one (`DROP TABLE users`), effectively deleting the users table from the database. The two dashes (`–`) at the end signify a comment, causing the system to ignore the rest of the original SQL query.
The actual consequence of the exploit will depend on the application’s structure and the database’s content and privileges.