CVE-2026-15693
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 · uneditedA security vulnerability has been detected in Tenda BE12 Pro 16.03.66.23. This issue affects the function fromSafeMacFilter of the file /goform/SafeMacFilter. The manipulation of the argument page leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.
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 · moderate confidenceStack-based buffer overflow in the Tenda BE12 Pro router's web interface (/goform/SafeMacFilter) in firmware 16.03.66.23. The 'page' parameter in the fromSafeMacFilter function lacks proper bounds checking, allowing remote attackers to overflow a stack buffer and potentially execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Tenda BE12 Pro modelAccess the router web interface and check the device model under System Status or Administration settings; alternatively, check the DHCP fingerprint or label on the deviceAffected if Device is not a Tenda BE12 Pro (different models may have similar vulnerabilities but this check targets this specific model)
-
Check firmware versionIn the router web interface, navigate to System Status or Administration > Firmware Upgrade to view the current firmware version; if telnet/ssh is available, run 'cat /proc/version' or 'ver' commandAffected if Firmware version is 16.03.66.23 (this is the only version explicitly listed as affected in the CVE summary)
-
Verify web interface accessibilityAttempt to access the router web interface at the default IP (typically 192.168.0.1 or 192.168.1.1) via HTTP/HTTPSAffected if Web interface is exposed to untrusted networks (the vulnerability is exploitable via the web interface)
-
Check SafeMacFilter endpoint availabilitySend a request to /goform/SafeMacFilter (e.g., GET http://<router_ip>/goform/SafeMacFilter) to confirm the endpoint exists and is reachableAffected if The SafeMacFilter feature is enabled and the /goform/SafeMacFilter endpoint is accessible (this is where the vulnerable fromSafeMacFilter function processes the 'page' parameter)
You are affected if you have a Tenda BE12 Pro router running firmware version 16.03.66.23 with the web interface and SafeMacFilter feature accessible to an attacker.
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 patch when available; until then, restrict web interface access to trusted networks only, disable SafeMacFilter if unused, and monitor for anomalous requests to /goform/SafeMacFilter.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15693 — 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-2026-15693 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