Skip to content
Fencer Intel
medium 5.2

CVE-2019-20738 json

Certain NETGEAR devices are affected by stored XSS.

published 6y ago modified 4mo ago also EUVD-2019-11277

cvss
5.2
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

Certain NETGEAR devices are affected by stored XSS. This affects D6100 before 1.0.0.58, D7800 before 1.0.1.34, JNR1010v2 before 1.1.0.50, JWNR2010v5 before 1.1.0.50, RBK50 before 2.3.5.30, RBR50 before 2.3.5.30, RBS50 before 2.3.5.30, R6020 before 1.0.0.30, R6080 before 1.0.0.30, R6100 before 1.0.1.16, R6120 before 1.0.0.40, R6700v2 before 1.2.0.14, R6800 before 1.2.0.14, R6900v2 before 1.2.0.14, R7500v2 before 1.0.3.26, R7800 before 1.0.2.46, R9000 before 1.0.4.2, WN3000RPv2 before 1.0.0.52, WN3000RPv3 before 1.0.2.78, WNDR3700v4 before 1.0.2.102, WNDR3700v5 before 1.1.0.54, WNDR4300v1 before 1.0.2.104, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.50, WNR2000v5 before 1.0.0.64, WNR2020 before 1.1.0.50, and WNR2050 before 1.1.0.50. NOTE: this may be a result of an incomplete fix for CVE-2017-18866.

Patch / fix

  • netgear d6100_firmware 1.0.0.58
  • netgear d7800_firmware 1.0.1.34
  • netgear jnr1010_firmware 1.1.0.50
  • netgear jwnr2010_firmware 1.1.0.50
  • netgear rbk50_firmware 2.3.5.30
  • netgear rbr50_firmware 2.3.5.30
  • netgear rbs50_firmware 2.3.5.30
  • netgear r6020_firmware 1.0.0.30
  • netgear r6080_firmware 1.0.0.30
  • netgear r6100_firmware 1.0.1.16
  • netgear r6120_firmware 1.0.0.40
  • netgear r6700_firmware 1.2.0.14
  • netgear r6800_firmware 1.2.0.14
  • netgear r6900_firmware 1.2.0.14
  • netgear r7500_firmware 1.0.3.26
  • netgear r7800_firmware 1.0.2.46
  • netgear r9000_firmware 1.0.4.2
  • netgear wn3000rp_firmware 1.0.0.52, 1.0.2.78
  • netgear wndr3700_firmware 1.0.2.102, 1.1.0.54
  • netgear wndr4300_firmware 1.0.0.48, 1.0.2.104

Is CVE-2019-20738 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 5.2 CVSS:3.0/AC:L/AV:A/A:N/C:L/I:L/PR:N/S:C/UI:R
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CNA 3.0 5.2 CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.