CVE-2026-5849
Path Traversal Vulnerability in Tenda i12 HTTP Handler
Publication date: 2026-04-09
Last updated on: 2026-04-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tenda | i12_firmware | 1.0.0.11(3862) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the Tenda i12 router version V1.0.0.11(3862) within its HTTP handler component. Specifically, it is a path traversal flaw in the R7WebsSecurityHandler function, which is supposed to enforce access control by allowing unauthenticated access only to certain URL prefixes (like "/public/" or "/lang/").
The function checks if the beginning of a URL matches a trusted prefix using a string comparison, but it does not properly validate or canonicalize the rest of the URL. An attacker can exploit this by crafting a URL that starts with a whitelisted prefix but includes directory traversal sequences ("../") to escape the restricted directory.
For example, a URL like "/public/../system_upgrade.asp" passes the whitelist check but actually accesses a sensitive administrative page. This allows an unauthenticated remote attacker to bypass login requirements and gain direct administrative access.
How can this vulnerability impact me? :
This vulnerability can have serious impacts because it allows an unauthenticated remote attacker to bypass authentication and gain full administrative access to the affected Tenda i12 router.
With this access, the attacker can manipulate router settings, potentially compromising network security, intercepting or redirecting traffic, and deploying further attacks within the network.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP GET requests that attempt to bypass authentication using path traversal sequences in the URL. Specifically, requests that start with a whitelisted prefix such as "/public/" but include directory traversal patterns like "../" to access sensitive administrative pages can indicate the presence of the vulnerability.
An example command using curl to test for this vulnerability is:
- curl -i -X GET "http://<target-ip>/public/../system_upgrade.asp"
If the response returns the administrative page content without redirecting to a login page (normally a 302 redirect), it indicates the vulnerability is present.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated remote attackers to bypass authentication and gain full administrative access to the Tenda i12 router. Such unauthorized access to administrative interfaces and sensitive resources can lead to unauthorized disclosure, modification, or destruction of data.
Because of this, organizations using the affected device may face challenges in maintaining compliance with common standards and regulations such as GDPR and HIPAA, which require strict access controls and protection of sensitive data.
Failure to prevent unauthorized access could result in violations of these regulations, potentially leading to legal penalties, data breaches, and loss of trust.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, restrict remote access to the Tenda i12 router's HTTP interface to trusted networks only, such as local management networks.
Avoid exposing the router's administrative interface to the internet or untrusted networks until a patch or update is available.
Monitor network traffic for suspicious requests that attempt path traversal sequences like '/../' in URLs targeting the router.
If possible, apply any available firmware updates or patches from the vendor that address this vulnerability.
Consider using network-level protections such as firewalls or access control lists to block unauthorized HTTP requests to the device.