Skip to main content
VulnerabilityPublished

CVE-2026-19683: TP-Link Systems ER7212PC v2 · Cleartext Transmission

Affects TP-Link Systems ER7212PC v2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.4.3 Build 20260722 Rel.40250 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.3 Build 20260722 Rel.40250, 2.4.4 Build 20260630 Rel.14398, 2.3.5 Build 20260625 Rel.43136 +16
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
TP-Link Systems Inc.ER7212PC v2Affected
  • =0
Fixed in
  • 2.4.3 Build 20260722 Rel.40250
TP-Link Systems Inc.ER605 v2Affected
  • =0
Fixed in
  • 2.4.4 Build 20260630 Rel.14398
TP-Link Systems Inc.ER7206 v2Affected
  • =0
Fixed in
  • 2.3.5 Build 20260625 Rel.43136
TP-Link Systems IncER7406 v1Affected
  • =0
Fixed in
  • 1.3.4 Build 20260625 Rel.43136
TP-Link Systems Inc.ER707-M2 v1Affected
  • =0
Fixed in
  • 1.4.4 Build 20260625 Rel.43063
TP-Link Systems IncER7412-M2 v1Affected
  • =0
Fixed in
  • 1.2.0 Build 20260630 Rel.82947

AI-suggested

If you cannot patch yet, users should consider disabling DDNS functionality if not required or ensure that network paths between the device and DDNS service are secured to prevent interception.

Description

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.

References

Community reviews

Loading reviews…