CVE-2026-13517
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 flaw has been found in Tenda JD12L 16.03.53.23. The impacted element is the function formWifiBasicSet of the file /goform/WifiBasicSet. Executing a manipulation of the argument security_5g can lead to stack-based buffer overflow. The attack may be launched remotely. The exploit has been published 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 confidenceTenda JD12L router firmware 16.03.53.23 contains a stack-based buffer overflow in the formWifiBasicSet function within /goform/WifiBasicSet. The security_5g parameter passed to this endpoint is not properly bounds-checked before use, allowing an attacker to overwrite stack memory via crafted input.
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/marketing material to confirm the model is Tenda JD12LAffected if Device is not a Tenda JD12L router - this CVE does not apply
-
Check firmware versionLog into the router web interface (typically at 192.168.0.1 or 192.168.1.1), navigate to System Settings or Status page, and locate the firmware version field. Alternatively, check via telnet/SSH if enabled or inspect firmware binary if extracted.Affected if Firmware version is 16.03.53.23 exactly, or if version cannot be determined but the device is confirmed as Tenda JD12L
-
Verify vulnerable endpoint existsAttempt to access the URL path /goform/WifiBasicSet on the router's web interface using a browser or HTTP tool (e.g., curl). A response (even an error) indicates the endpoint exists; a 404 indicates it may not be present in this firmware variant.Affected if The /goform/WifiBasicSet endpoint returns any response, indicating it is present in the firmware
-
Check remote web management exposureVerify whether the router's web administration interface is accessible from WAN/external IP addresses. Check router settings under Advanced or Security settings for 'Remote Management' or 'Web Management' access from WAN. Use an external host or port scanner targeting the router's public IP on ports 80/443.Affected if Remote web management is enabled and the router's WAN IP is reachable on HTTP/HTTPS ports, exposing the vulnerable endpoint to external attackers
User is affected if they have a Tenda JD12L router running firmware 16.03.53.23 with the /goform/WifiBasicSet endpoint present and the web management interface accessible from their network or WAN.
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; if no patch exists, disable remote web management or replace the device. Implement network segmentation to limit exposure of the management interface.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13517 — 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-13517 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