totolink a702r firmware

Name: totolink a702r firmware
Brand: totolink

productUS

cpe:2.3:o:totolink:a702r_firmware:*:*:*:*:*:*:*:*

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

KEV-listed

by severity

1critical5high1medium0low

updated 2026-10-28

vulnerabilities (32)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2020-27368US	medium5.5	0.46% (40th)	Exploit	no fix	2021-01-14	= 1.0.0-b20161227.1023
CVE-2019-19825US	critical9.8	29.6% (98th)	—	no fix	2020-01-27	≤ 2.1.3
CVE-2019-19824US	high8.8	25.1% (98th)	—	no fix	2020-01-27	≤ 2.1.3
CVE-2025-8140US	—	11.3% (96th)	—	no fix	2025-07-25	= 4.0.0-b20230721.1521
CVE-2025-8138US	—	11.3% (96th)	—	no fix	2025-07-25	= 4.0.0-b20230721.1521
CVE-2019-19822US	high7.5OT elevated	8.67% (95th)	—	no fix	2020-01-27	≤ 2.1.3
CVE-2019-19823US	high7.5	6.41% (94th)	—	no fix	2020-01-27	≤ 2.1.3
CVE-2025-6627US	—	5.67% (93rd)	—	no fix	2025-06-25	= 4.0.0-b20230721.1521
CVE-2025-8136US	high7.5	1.23% (69th)	—	no fix	2025-07-25	= 4.0.0-b20230721.1521
CVE-2025-8139US	—	1.23% (69th)	—	no fix	2025-07-25	= 4.0.0-b20230721.1521
CVE-2025-8137US	—	1.23% (69th)	—	no fix	2025-07-25	= 4.0.0-b20230721.1521
CVE-2025-6393US	high7.5	1.05% (64th)	—	no fix	2025-06-21	= 4.0.0-b20230721.1521
CVE-2025-6825US	—	0.99% (63rd)	—	no fix	2025-06-28	= 4.0.0-b20230721.1521
CVE-2025-6147US	—	0.98% (62nd)	—	no fix	2025-06-17	= 4.0.0-b20230721.1521
CVE-2025-6940US	—	0.96% (61st)	—	no fix	2025-07-01	= 4.0.0-b20230721.1521
CVE-2025-4835US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4834US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4833US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4832US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4831US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4830US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4829US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4827US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4826US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4825US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4824US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-4823US	—	0.85% (58th)	—	no fix	2025-05-17	= 3.0.0-b20230809.1615
CVE-2025-9783US	—	0.66% (52nd)	—	no fix	2025-09-01	= 4.0.0-b20211108.1423
CVE-2025-9782US	—	0.66% (52nd)	—	no fix	2025-09-01	= 4.0.0-b20211108.1423
CVE-2025-9781US	—	0.66% (52nd)	—	no fix	2025-09-01	= 4.0.0-b20211108.1423
CVE-2025-9780US	—	0.66% (52nd)	—	no fix	2025-09-01	= 4.0.0-b20211108.1423
CVE-2025-9779US	—	0.66% (52nd)	—	no fix	2025-09-01	= 4.0.0-b20211108.1423

weaknesses (7)

The flaw types (CWEs) most of these CVEs share.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer27 CVEs
CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')27 CVEs
CWE-287Improper Authentication1 CVEs
CWE-306Missing Authentication for Critical Function1 CVEs
CWE-522Insufficiently Protected Credentials1 CVEs
CWE-552Files or Directories Accessible to External Parties1 CVEs
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')1 CVEs

sources (1)

Which sources assert this record, and when.

USNVD / CVE32 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan