How severe is CVE-2025-4829?

CVE-2025-4829 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-4829 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-4829?

CVE-2025-4829 primarily affects Totolink A702r Firmware. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-4829?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-4829 have an EU (EUVD) identifier?

Yes. CVE-2025-4829 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-15583.

When was CVE-2025-4829 published?

CVE-2025-4829 was published on 2025-05-17 and last updated on 2026-06-17.

CVE-2025-4829

CVE-2025-4829 is a high-severity vulnerability in Totolink A702r Firmware with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-120.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 9.0
CVSS v4: 8.7
EPSS exploit prediction: 1% (47th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-15583
Weakness: CWE-120
Affected product: Totolink A702r Firmware
Published: 2025-05-17
Last modified: 2026-06-17

Description

A vulnerability classified as critical was found in TOTOLINK A702R, A3002R and A3002RU 3.0.0-B20230809.1615. Affected by this vulnerability is the function sub_40BE30 of the file /boafrm/formStats of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Frequently asked questions

What is CVE-2025-4829?: A vulnerability classified as critical was found in TOTOLINK A702R, A3002R and A3002RU 3.0.0-B20230809.1615. Affected by this vulnerability is the function sub_40BE30 of the file /boafrm/formStats of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
How severe is CVE-2025-4829?: CVE-2025-4829 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-4829 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-4829?: CVE-2025-4829 primarily affects Totolink A702r Firmware. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-4829?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-4829 have an EU (EUVD) identifier?: Yes. CVE-2025-4829 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-15583.
When was CVE-2025-4829 published?: CVE-2025-4829 was published on 2025-05-17 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:o:totolink:a702r_firmware:3.0.0-b20230809.1615:*:*:*:*:*:*:*
cpe:2.3:o:totolink:a3002r_firmware:3.0.0-b20230809.1615:*:*:*:*:*:*:*
cpe:2.3:o:totolink:a3002ru_firmware:3.0.0-b20230809.1615:*:*:*:*:*:*:*

More vulnerabilities in Totolink A702r Firmware

CVE-2019-19825 — Critical (CVSS 9.8): On certain TOTOLINK Realtek SDK based routers, the CAPTCHA text can be retrieved via an…
CVE-2025-9783 — High (CVSS 8.8): A vulnerability was determined in TOTOLINK A702R 4.0.0-B20211108.1423. This issue affects the function sub_418030 of…
CVE-2025-9782 — High (CVSS 8.8): A vulnerability was found in TOTOLINK A702R 4.0.0-B20211108.1423. This vulnerability affects the function sub_4466F8 of…
CVE-2025-9781 — High (CVSS 8.8): A vulnerability has been found in TOTOLINK A702R 4.0.0-B20211108.1423. This affects the function sub_4162DC of the file…
CVE-2025-9780 — High (CVSS 8.8): A flaw has been found in TOTOLINK A702R 4.0.0-B20211108.1423. Affected by this issue is the function sub_419BE0 of the…
CVE-2025-9779 — High (CVSS 8.8): A vulnerability was detected in TOTOLINK A702R 4.0.0-B20211108.1423. Affected by this vulnerability is the function…

All CVEs affecting Totolink A702r Firmware →

Other CWE-120 (Classic Buffer Overflow) vulnerabilities

CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2026-24823 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in FASTSHIFT…
CVE-2026-24810 — Critical (CVSS 10.0): Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in rethinkdb (src/cjson modules).…
CVE-2026-24800 — Critical (CVSS 10.0): Out-of-bounds Write, Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in tildearrow…
CVE-2025-9962 — Critical (CVSS 10.0): A buffer overflow vulnerability in Novakon P series allows attackers to gain root permission without prior…
CVE-2010-10016 — Critical (CVSS 10.0): BS.Player version 2.57 (build 1051) contains a vulnerability in its playlist import functionality. When processing .m3u…

Browse all CWE-120 (Classic Buffer Overflow) vulnerabilities →