CVE-2025-7952
TOTOLINK T6 MQTT Packet wireless.so ckeckKeepAlive command injection
CVSS v3
6.3
MEDIUM
EPSS Score
20.9 %
exploit probability, as of 2026-10-11
CISA KEV
No
known exploited
Exploitation
poc
SSVC status
Affected and fixed versions
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2025-7952 yet.
Description
A vulnerability classified as critical was found in TOTOLINK T6 4.1.5cu.748. This vulnerability affects the function ckeckKeepAlive of the file wireless.so of the component MQTT Packet Handler. The manipulation leads to command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Published
- 2025-07-22
- Last Modified
- 2026-04-29
Frequently asked questions
What is CVE-2025-7952?
A vulnerability classified as critical was found in TOTOLINK T6 4.1.5cu.748. This vulnerability affects the function ckeckKeepAlive of the file wireless.so of the component MQTT Packet Handler. The manipulation leads to command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Is CVE-2025-7952 actively exploited?
A proof-of-concept exploit exists for CVE-2025-7952, but active exploitation has not been confirmed at this time.
What is the CVSS score for CVE-2025-7952?
CVE-2025-7952 has a CVSS v3 base score of 6.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
Running TOTOLINK T6? Hear about its next vulnerability
CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.
Already have an account? Open CVE Watch
No credit card required · 50 free checks/month · Free API key
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? CVE Watch alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.