CVE-2026-24439
BaseFortify
Publication date: 2026-01-26
Last updated on: 2026-01-28
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tenda | w30e_firmware | to 16.01.0.19\(5037\) (inc) |
| tenda | w30e | 2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-116 | The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Shenzhen Tenda W30E V2 router firmware versions up to V16.01.0.19(5037) because the device's web management interfaces do not include the X-Content-Type-Options: nosniff HTTP response header. Without this header, browsers may perform MIME sniffing and incorrectly interpret attacker-controlled responses as executable scripts, potentially leading to security issues. [1]
How can this vulnerability impact me? :
The vulnerability can allow attackers to exploit the lack of the X-Content-Type-Options: nosniff header to trick browsers into executing malicious scripts by misinterpreting the content type of responses from the router's web management interface. This can lead to security risks such as cross-site scripting or other script-based attacks, although the overall severity is low. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by inspecting the HTTP response headers of the web management interface of the Shenzhen Tenda W30E V2 router. Specifically, check if the 'X-Content-Type-Options: nosniff' header is missing. This can be done using tools like curl or browser developer tools. For example, use the command: curl -I http://<router-ip>/ and look for the absence of the 'X-Content-Type-Options' header in the response. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the router firmware to a version later than V16.01.0.19(5037) if available, as this version lacks the necessary security header. If an update is not available, restrict access to the web management interface to trusted networks only and avoid using the interface over untrusted networks. Additionally, monitor for any suspicious activity and consider using network-level protections such as firewalls to limit exposure. [1]