CVE-2026-15692
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 weakness has been identified in Tenda BE12 Pro 16.03.66.23. This vulnerability affects the function fromSafeUrlFilter of the file /goform/SafeUrlFilter. Executing a manipulation of the argument page can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.
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 Tenda BE12 Pro router firmware 16.03.66.23 within the fromSafeUrlFilter function in /goform/SafeUrlFilter. The 'page' parameter lacks proper bounds checking, allowing remote attackers to potentially overwrite stack memory and 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.
-
Identify device modelAccess the router admin interface or check the device label to confirm the model is Tenda BE12 ProAffected if Device is not a Tenda BE12 Pro router, then it is not affected by this specific CVE
-
Check firmware versionLog into the router admin panel and navigate to System Settings or Firmware Upgrade page to view the installed firmware version, or use the command 'cat /proc/version' if telnet/ssh access is availableAffected if Firmware version is 16.03.66.23 exactly, as this is the specific version mentioned in the CVE
-
Verify SafeUrlFilter endpoint existsAttempt to access or probe the /goform/SafeUrlFilter endpoint on the router (typically via HTTP GET or POST to the router's IP address with this path)Affected if The endpoint responds, indicating the vulnerable function exists on the device
-
Confirm remote management is accessibleCheck if the router's web interface is reachable from the WAN/internet side, or check the router's firewall/remote management settings to see if external access to /goform/* endpoints is permittedAffected if Remote management or the web interface is exposed to WAN, allowing remote attackers to reach the vulnerable endpoint
-
Inspect for exploitation indicatorsReview router system logs or web server logs for unusual POST requests to /goform/SafeUrlFilter with abnormally long 'page' parameter values, or check for unexpected new admin accounts or configuration changesAffected if Logs show suspicious requests to SafeUrlFilter or unexplained system changes
The device is affected if it is a Tenda BE12 Pro running firmware version 16.03.66.23 with the SafeUrlFilter feature accessible, particularly if remote management is enabled.
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; if no patch exists, disable remote management interfaces, segment affected devices on isolated VLANs, and monitor for exploit attempts.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15692 — 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-15692 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