dbcve.org
Wac510 FirmwareOperating system · Netgear

CVE-2019-20742

MEDIUM · 5.2 CVSS v3.1 Published 2020-04-16
Fix available
A fix is available. Upgrade to 8.0.1.3 or later.
See remediation →
55/100
Remediation priority · Elevated
No privileges

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
NETGEAR WAC510 devices before 8.0.1.3 are affected by stored XSS.

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 · high confidence

NETGEAR WAC510 wireless access point devices before firmware version 8.0.1.3 contain a stored cross-site scripting (XSS) vulnerability. An authenticated attacker can inject malicious JavaScript code into the device's web management interface, which is then persistently stored and executed when other users access the affected pages.

MitigationUpgrade NETGEAR WAC510 firmware to version 8.0.1.3 or later to remediate the stored XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wac510 FirmwareOperating system
Affected:< 8.0.1.3

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Confirm device model is WAC510
    Log into the web management interface and check the device model name in the status/dashboard page, or check the physical device label
    Affected if Device is not a NETGEAR WAC510
  2. Check firmware version
    In the web management interface, navigate to the Maintenance or System section and locate the firmware version field. Alternatively, check the login page footer or a dedicated 'About' page
    Affected if Firmware version is less than 8.0.1.3 (for example, 8.0.0.0, 7.x.x.x, or any version below 8.0.1.3)
  3. Verify web management interface is enabled
    Check if the HTTP/HTTPS web management interface is accessible on the device by attempting to reach the device's IP address in a browser
    Affected if Web management interface is enabled and the device runs a vulnerable firmware version below 8.0.1.3

A user is affected if they have a NETGEAR WAC510 device running firmware version 8.0.1.3 or lower, with the web management interface enabled.

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
Upgrade available Upgrade to 8.0.1.3 or later
Fixed in 8.0.1.3
Interim mitigation

Upgrade NETGEAR WAC510 firmware to version 8.0.1.3 or later to remediate the stored XSS vulnerability.

Fix this in Wac510 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-20742 — 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-2019-20742 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