cve.bz

CVE-2026-19683 tp-link

6.3 mediumEPSS 0.3%

Medium (6.3) in tp-link. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability exists in the Dynamic DNS (DDNS) functionality of TP-Link Omada Gateways. During communication with a third-party DDNS service, authentication credentials are transmitted over an unencrypted channel. An attacker who can observe or manipulate traffic between an affected device and the DDNS service may obtain sensitive authentication information or interfere with DDNS update operations. Exploitation requires DDNS to be configured, communication with an external DDNS service, and attacker visibility or control of the relevant network path.  Successful exploitation may result in disclosure of DDNS account credentials, unauthorized access to DDNS management functionality, or modification of DNS records associated with the affected deployment.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-319 Cleartext Transmission of Sensitive Information
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-19683 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-19683?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-19683?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-19683 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-19683

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-19683](https://cve.bz/cve/badge/CVE-2026-19683.svg)](https://cve.bz/cve/CVE-2026-19683)

HTML:

<a href="https://cve.bz/cve/CVE-2026-19683"><img src="https://cve.bz/cve/badge/CVE-2026-19683.svg" alt="CVE-2026-19683"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. ER7212PC v2before 2.4.3 Build 20260722 Rel.40250
TP-Link Systems Inc. ER605 v2before 2.4.4 Build 20260630 Rel.14398
TP-Link Systems Inc. ER7206 v2before 2.3.5 Build 20260625 Rel.43136
TP-Link Systems Inc ER7406 v1before 1.3.4 Build 20260625 Rel.43136
TP-Link Systems Inc. ER707-M2 v1before 1.4.4 Build 20260625 Rel.43063
TP-Link Systems Inc ER7412-M2 v1before 1.2.0 Build 20260630 Rel.82947
TP-Link Systems Inc. ER8411 v1before 1.4.1 Build 20260708 Rel.64832
TP-Link Systems Inc. ER706W v1before 1.2.11 Build 20260723 Rel.41567
TP-Link Systems Inc. v1before 1.2.6 Build 20260723 Rel.41321
TP-Link Systems Inc. ER706W-4G v2before 2.1.11 Build 20260723 Rel.41624
TP-Link Systems Inc. ER706WP-4G v1before 1.1.11 Build 20260723 Rel.41624
TP-Link Systems Inc. ER703WP-4G-Outdoor v1before 1.1.7 Build 20260723 Rel.41712
TP-Link Systems Inc. DR3220v-4G v1before 1.2.0 Build 20260630 Rel.82652
TP-Link Systems Inc. DR3650v v1before 1.2.0 Build 20260630 Rel.83311
TP-Link Systems Inc. DR3650v-4G v1before 1.2.0 Build 20260630 Rel.83347
TP-Link Systems Inc. ER603WP-4G-Outdoor v1before 1.0.2 Build 20260723 Rel.43271
TP-Link Systems Inc. DR3150 v1before 1.0.1 Build 20260722 Rel.16854
TP-Link Systems Inc. ER701-5G-Outdoor v1before 1.0.3 Build 20260723 Rel.40931
TP-Link Systems Inc. ER605W v2before 2.0.4 Build 20260723 Rel.43763

Attack patterns (CAPEC)

  • CAPEC-65 Sniff Application Code Likelihood: Low · Severity: High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-117 Interception Likelihood: Low · Severity: Medium
  • CAPEC-383 Harvesting Information via API Event Monitoring Severity: Low
  • CAPEC-477 Signature Spoofing by Mixing Signed and Unsigned Content Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON