dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-13519

HIGH · 8.8 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 · unedited
A vulnerability was found in Tenda JD12L 16.03.53.23. This impacts the function fromNatStaticSetting of the file /goform/NatStaticSetting. The manipulation of the argument page results in stack-based buffer overflow. The attack can be executed remotely. The exploit has been made public and could 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 confidence

A stack-based buffer overflow vulnerability exists in the fromNatStaticSetting function of the Tenda JD12L router firmware (version 16.03.53.23). The vulnerability is located in the /goform/NatStaticSetting web endpoint where manipulation of the 'page' argument allows overflowing a stack-based buffer, potentially enabling remote code execution.

MitigationRestrict network access to the router's web administration interface, disable remote management if exposed to the internet, and apply any vendor firmware updates when available. Network segmentation can limit exposure while awaiting a fix.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Tenda JD12L router device
    Check the router model number via the web interface status page, device label, or by accessing the admin panel at the router's IP address and looking for the device model information.
    Affected if The device model is not Tenda JD12L, then it is not affected by this specific CVE.
  2. Verify the firmware version is 16.03.53.23
    Access the router's web administration interface, navigate to the System Settings or Firmware Upgrade page, and check the displayed firmware version. Alternatively, check via command line if telnet/ssh access is available.
    Affected if The installed firmware version is exactly 16.03.53.23, indicating it matches the affected version.
  3. Confirm the web interface is enabled and accessible
    Attempt to access the router's web interface by navigating to the router's IP address (commonly 192.168.0.1 or 192.168.1.1) in a web browser. Verify the login page loads for /goform/NatStaticSetting or check if the web server responds.
    Affected if The web interface is accessible on the local network or exposed remotely, which is required for exploitation of this vulnerability.
  4. Check for the vulnerable NatStaticSetting endpoint
    Send an HTTP GET or POST request to http://<router_ip>/goform/NatStaticSetting and observe the response. A valid endpoint may return a 200 OK or redirect; a non-existent endpoint may return 404.
    Affected if The /goform/NatStaticSetting endpoint responds to requests, indicating the vulnerable feature is present in the firmware.
  5. Identify if remote management is enabled
    In the router's web interface, check the System Settings or Advanced settings for 'Remote Management' or 'Remote Access' options. Determine if remote management over WAN is enabled.
    Affected if Remote management is enabled and the router's web interface is accessible from the internet, increasing the attack surface for remote exploitation.

The environment is affected if the device is a Tenda JD12L router running firmware version 16.03.53.23 with the web interface accessible and the /goform/NatStaticSetting endpoint present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the router's web administration interface, disable remote management if exposed to the internet, and apply any vendor firmware updates when available. Network segmentation can limit exposure while awaiting a fix.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13519 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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