CVE-2019-19825 in the critical feed json
On certain TOTOLINK Realtek SDK based routers, the CAPTCHA text can be retrieved via an {"topicurl":"setting/getSanvas"} POST to the boafrm…
published 2020-01-27 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-9423
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 29.6%
- EPSS 29.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
On certain TOTOLINK Realtek SDK based routers, the CAPTCHA text can be retrieved via an {"topicurl":"setting/getSanvas"} POST to the boafrm/formLogin URI, leading to a CAPTCHA bypass. (Also, the CAPTCHA text is not needed once the attacker has determined valid credentials. The attacker can perform router actions via HTTP requests with Basic Authentication.) This affects A3002RU through 2.0.0, A702R through 2.1.3, N301RT through 2.1.6, N302R through 3.4.0, N300RT through 3.4.0, N200RE through 4.0.0, N150RT through 3.4.0, and N100RE through 3.4.0.
Exploit prediction
29.56% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template TOTOLINK/Realtek Routers - CAPTCHA Bypass nuclei detection template
- sploit.tech https://sploit.tech referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
sploit.tech
exploit, third-party-advisory
-
seclists.org
/fulldisclosure/2020/Jan/36
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/156083/Realtek-SDK-Information-Disclosure-Code-Execution.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2020/Jan/38
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-19825
- NVD CVE-2019-19825
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.