CVE-2025-9303 is a high severity (8.8) buffer overflow in TOTOLINK A720R firmware, affecting firmware 4.1.5cu.630_B20250509. No fixed version is confirmed. Until a fix is confirmed, restrict who can reach the device, review the affected code path, and scan your dependencies.
What's affected
- Product: TOTOLINK A720R firmware
- Affected versions: firmware 4.1.5cu.630_B20250509
- Component:
/cgi-bin/cstecgi.cgi (function setParentalRules) - Parameter: the
descparameter - Severity: High, CVSS 8.8 (
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) - Weakness classes: CWE-119, CWE-120
- Fixed version: No fixed version is confirmed, so the vendor advisory or release page should be checked
The NVD description says the desc parameter is copied into a fixed size buffer without a safe length check. It also says the attack can be started remotely and that an exploit has been made public. The record does not list a fixed version, and the reference pages we could reach did not either.
This is device firmware. Fixes, if any, arrive as a vendor firmware image rather than a package update.
The public report we read describes the same product, file and parameter as the record, so we found no conflict in affected versions or severity between the two. Severity above is the score in the record. The advisory text itself gives no separate score.
How to check if you're exposed
Log in to the device's own management page and read the firmware version. Compare it with the affected range (firmware 4.1.5cu.630_B20250509). The record names that build, and the advisory does not say which other builds are or are not affected.
Next, find out whether the management interface is reachable from outside your network. From a machine outside the network, check whether the management port answers at all. If it does, that is the first thing to change.
Check the vendor's support page for a newer firmware image and its release notes. There is no package manager command that covers this, so the vendor page is the source of truth.
What to do now
- Find it. Work out whether TOTOLINK A720R firmware is installed anywhere in your estate, including test servers and old demos.
- Limit exposure. Put the application behind a VPN or an IP allowlist, or take it offline if nobody needs it.
- Look for a fix. Check the vendor's site or repository for a newer release. If none exists, ask the vendor directly and record the answer.
- Reduce the reach. Disable remote management where you can and keep the device off the public internet until the vendor ships a firmware fix.
- Watch the logs. Keep web server logs for the affected path and review them for odd input.
- Scan. Run your dependency manifest through the free in-browser dependency scan to see what else is exposed.
Why it matters
A buffer overflow (CWE-119, CWE-120) happens when code copies more data than a fixed size space can hold. The extra data overwrites neighbouring memory, which can crash the program or change how it runs. In router firmware, the web management program runs with high privilege, so a flaw there can matter a lot.
The record scores this 8.8 because a low privilege login is enough and the impact on the device is high. Home and small office routers are rarely patched on a schedule, which is why limiting remote management matters while you wait for the vendor.
The record shows the CISA Known Exploited Vulnerabilities flag as false, and nothing we read reports use in real attacks. The NVD description does say a proof of concept is public, which lowers the effort for anyone who wants to try it. Treat it as exposed if the product is reachable.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is a patch available?
The record and the report we read name no fixed release, so check the vendor's site for a newer version before assuming you are covered. Check the vendor page again before you act, because this can change.
Does this CVE mean attackers are using it now?
Not according to the sources we read. The CISA KEV flag in the record is false. The NVD description does say an exploit is public, so exposure is still worth treating seriously.
Sources
- NVD record and Safeguard Gold entry for CVE-2025-9303
- Public vulnerability report for this CVE
- Other references in the record, including VulDB, could not be retrieved when we checked.
Last reviewed: 18 October 2026.
