CVE-2026-11504
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 vulnerability was detected in Tenda CX12L 16.03.53.12. The impacted element is the function setSchedWifi of the file /goform/openSchedWifi of the component Wi-Fi Schedule Configuration Endpoint. Performing a manipulation of the argument schedStartTime/schedEndTime results in stack-based buffer overflow. The attack may be initiated remotely. The exploit is now public 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 Tenda CX12L router firmware 16.03.53.12 allows remote attackers to overflow the stack via the schedStartTime/schedEndTime parameters in the /goform/openSchedWifi endpoint's setSchedWifi function, potentially enabling remote code execution.
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 the router modelAccess the router's web admin interface or check the device label to confirm it is a Tenda CX12L modelAffected if The device is a Tenda CX12L router
-
Check the 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' via telnet/SSH if availableAffected if The firmware version is 16.03.53.12
-
Confirm Wi-Fi scheduling is enabledNavigate to the Wi-Fi Settings or Wi-Fi Schedule section in the router web interface and check if any schedule is currently active or configuredAffected if Wi-Fi scheduling is enabled and configured with schedule rules
-
Test for the vulnerable endpointSend a crafted HTTP POST request to http://[router-ip]/goform/openSchedWifi with excessively long strings in the schedStartTime and schedEndTime parameters to observe if the device responds or crashesAffected if The device accepts the request without proper bounds checking (vulnerable behavior would be a crash, hang, or unexpected response)
-
Review for signs of compromiseCheck the router's system logs or status page for any unexpected changes to Wi-Fi schedule settings, unfamiliar admin accounts, or unexplained device behaviorAffected if Logs show unauthorized changes to Wi-Fi scheduling configuration or evidence of buffer overflow crashes
A user is affected if they have a Tenda CX12L router running firmware version 16.03.53.12 with Wi-Fi scheduling enabled, as this combination exposes the vulnerable openSchedWifi endpoint with unchecked schedStartTime and schedEndTime parameters.
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 update when available; until then, restrict administrative access to the router's web interface to trusted networks only, or disable the Wi-Fi schedule feature if not needed.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11504 — 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-11504 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