Tenda W30E V2 up to 16.01.0.19(5037) Maintenance Interface unverified password change
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Tenda W30E V2 up to 16.01.0.19(5037). This impacts an unknown function of the component Maintenance Interface. This manipulation causes unverified password change. This vulnerability is handled as CVE-2026-24440. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in Tenda W30E V2 up to 16.01.0.19(5037). Affected by this vulnerability is some unknown processing of the component Maintenance Interface. The manipulation with an unknown input leads to a unverified password change vulnerability. The CWE definition for the vulnerability is CWE-620. When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Shenzhen Tenda W30E V2 firmware versions up to and including V16.01.0.19(5037) allow account passwords to be changed through the maintenance interface without requiring verification of the existing password. This enables unauthorized password changes when access to the affected endpoint is obtained.
The weakness was released by Kazuma Matsumoto. The advisory is shared at tendacn.com. This vulnerability is known as CVE-2026-24440 since 01/22/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/29/2026). MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-4677). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.tenda.com.cn/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Unverified password changeCWE: CWE-620 / CWE-640
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/22/2026 CVE reserved01/27/2026 Advisory disclosed
01/27/2026 VulDB entry created
01/29/2026 VulDB entry last update
Sources
Vendor: tenda.com.cnAdvisory: tendacn.com
Researcher: Kazuma Matsumoto
Status: Not defined
CVE: CVE-2026-24440 (🔒)
GCVE (CVE): GCVE-0-2026-24440
GCVE (VulDB): GCVE-100-342901
EUVD: 🔒
Entry
Created: 01/27/2026 02:04Updated: 01/29/2026 03:13
Changes: 01/27/2026 02:04 (66), 01/29/2026 02:48 (1), 01/29/2026 03:13 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.