CVE-2025-25662
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTenda O4 V3.0 V1.0.0.10(2936) is vulnerable to Buffer Overflow in the function SafeSetMacFilter of the file /goform/setMacFilterList via the argument remark/type/time.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA buffer overflow vulnerability exists in the SafeSetMacFilter function of Tenda O4 V3.0 V1.0.0.10(2936) routers in the /goform/setMacFilterList endpoint. The vulnerability is triggered through insufficient bounds checking on the remark, type, or time parameters, allowing remote attackers to potentially overwrite memory and execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0.10\(2936\)CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the router web interface or check the device label to confirm it is a Tenda O4 router. Alternatively, check the DHCP client table or network discovery for the device hostname or MAC OUI.Affected if The device is not a Tenda O4 router, then it is not affected by this specific CVE.
-
Check the firmware versionAccess the router admin panel, typically at 192.168.0.1 or 192.168.1.1, then navigate to System Settings > Firmware Upgrade or Administration > System Management to view the installed firmware version. Alternatively, use the router's API or check the sysinfo endpoint if available.Affected if The installed firmware is exactly version 1.0.0.10(2936), then the device is affected. If the version differs (higher or lower), it is not affected by this specific CVE.
-
Confirm the vulnerable endpoint existsAttempt to access the /goform/setMacFilterList endpoint by sending an HTTP GET or POST request to the router's IP address on port 80 or 8080. For example: curl http://<router_ip>/goform/setMacFilterListAffected if The endpoint responds (even with an error), it indicates the web interface is running and the vulnerable code path exists.
-
Verify Mac Filter feature is accessibleLog into the router admin panel and navigate to the Mac Filter or Access Control settings page. Check if the Mac Filter feature is present and can be configured.Affected if The Mac Filter feature exists and is accessible through the web interface, the vulnerable SafeSetMacFilter function can be triggered.
The device is affected only if it is a Tenda O4 router running firmware version 1.0.0.10(2936) with the web management interface accessible and the Mac Filter feature available.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates when available; until then, restrict access to the router's web management interface to trusted networks only using firewall rules or ACLs.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-25662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data