Cross‑Site Request Forgery in Dbit N300 T1 Pro Router Web Management
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
| AND |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dbit | N300 T1 Pro Wireless Router |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.163% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/kirubel-cve/CVE-2026-36956 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dbitnet
Dbitnet dbit N300 T1 Pro Dbitnet dbit N300 T1 Pro Firmware |
|
| CPEs | cpe:2.3:h:dbitnet:dbit_n300_t1_pro:-:*:*:*:*:*:*:* cpe:2.3:o:dbitnet:dbit_n300_t1_pro_firmware:1.0.0:*:*:*:*:*:*:* |
|
| Vendors & Products |
Dbitnet
Dbitnet dbit N300 T1 Pro Dbitnet dbit N300 T1 Pro Firmware |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Site Request Forgery in Dbit N300 T1 Pro Router Web Management |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dbit
Dbit n300 T1 Pro Wireless Router |
|
| Vendors & Products |
Dbit
Dbit n300 T1 Pro Wireless Router |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-352 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A Cross-Site Request Forgery (CSRF) vulnerability exists in the web management interface of the Dbit N300 T1 Pro wireless router V1.0.0. The router fails to implement proper CSRF protection mechanisms such as anti-CSRF tokens or strict Origin/Referer validation for administrative API endpoints. An attacker can craft a malicious webpage that sends forged HTTP requests to configuration endpoints such as /api/setWlan. If an authenticated administrator visits the malicious webpage, the victim's browser automatically includes the valid session cookie in the request, allowing the router to process the request as a legitimate administrative action. | |
| References |
|