dbcve.org
R6900 FirmwareOperating system · Netgear

CVE-2023-30280

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Buffer Overflow vulnerability found in Netgear R6900 v.1.0.2.26, R6700v3 v.1.0.4.128, R6700 v.1.0.0.26 allows a remote attacker to execute arbitrary code and cause a denial ofservice via the getInputData parameter of the fwSchedule.cgi page.

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

A buffer overflow vulnerability in the getInputData parameter of fwSchedule.cgi on Netgear R6900 (v1.0.2.26), R6700v3 (v1.0.4.128), and R6700 (v1.0.0.26) routers allows remote attackers to execute arbitrary code or cause denial of service via crafted input.

MitigationApply vendor-supplied firmware updates to the affected router models; if unavailable, disable remote web management access or place devices behind a firewall to limit exposure.

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
R6900 FirmwareOperating system
Affected:= 1.0.2.26
R6700 FirmwareOperating system
Affected:= 1.0.0.26= 1.0.4.128

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 router model
    Access router administration interface or check device label to confirm the model is Netgear R6900, R6700v3, or R6700
    Affected if Router model is one of the three affected models
  2. Check firmware version
    Navigate to router web interface (typically 192.168.1.1), look in Administration > Firmware Update or similar section to find the installed firmware version
    Affected if Firmware version equals 1.0.2.26 (R6900), 1.0.0.26 (R6700), or 1.0.4.128 (R6700/R6700v3)
  3. Verify remote web management is enabled
    Check router settings under Remote Management or Access Control; look for options like Enable Remote Management, Web Service, or External access
    Affected if Remote web management access is enabled, making the device reachable from the internet on HTTP/HTTPS ports
  4. Test fwSchedule.cgi accessibility
    From an external network (or using router IP if remote access is on), attempt to access fwSchedule.cgi endpoint - typically via browser or curl to the router's public IP on ports 80/443
    Affected if The fwSchedule.cgi script is reachable and responds to requests, indicating the vulnerable component is exposed

A user is affected if they own a Netgear R6900, R6700v3, or R6700 router running the specific vulnerable firmware versions (1.0.2.26, 1.0.0.26, or 1.0.4.128) with remote web management enabled and the fwSchedule.cgi endpoint exposed to the attacker.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates to the affected router models; if unavailable, disable remote web management access or place devices behind a firewall to limit exposure.

Recommended fix Moderate confidence

Netgear R6900/R6700 latest firmware (contact Netgear support for specific version numbers)

  1. 1. Visit the official Netgear support website at www.netgear.com/support/
  2. 2. Enter your specific router model (R6900 or R6700) to access the firmware download page
  3. 3. Download the latest available firmware version for your router model
  4. 4. Access your router's web management interface (typically at 192.168.1.1)
  5. 5. Navigate to the Administration or Advanced settings section
  6. 6. Select the firmware upgrade option and upload the downloaded firmware file
  7. 7. Wait for the upgrade to complete - do not power off the router during this process
  8. 8. After reboot, verify the new firmware version in the router status page
Caveat Standard firmware upgrade - backup configuration before upgrading; router will briefly reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in R6900 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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