CVE-2024-51021
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 · uneditedNetgear XR300 v1.0.3.78, R7000P v1.3.3.154, and R6400 v2 1.0.4.128 was discovered to contain a command injection vulnerability via the wan_gateway parameter at genie_fix2.cgi. This vulnerability allows attackers to execute arbitrary OS commands via a crafted request.
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 confidenceCommand injection vulnerability in Netgear router web interface (genie_fix2.cgi) allows remote attackers to execute arbitrary OS commands through the wan_gateway parameter without proper input sanitization.
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= 1.0.3.78= 1.3.3.154= 1.0.4.128CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLog into the router web interface or check the device label/menu to confirm the exact model (XR300, R7000p, or R6400v2)Affected if Model is not one of: XR300, R7000p, or R6400v2 (those are the only affected models)
-
Check firmware versionAccess router administration panel, typically at 192.168.1.1, and navigate to Administration > Firmware Update or Router Status to find the installed firmware versionAffected if Firmware version exactly matches 1.0.3.78 (XR300), 1.3.3.154 (R7000p), or 1.0.4.128 (R6400v2)
-
Verify genie_fix2.cgi endpoint existsAttempt to access the CGI script via router web interface URL path /genie_fix2.cgi (requires web interface to be reachable)Affected if The endpoint responds or exists on the device - vulnerability is only present if this CGI file exists with the flawed parameter handling
-
Confirm wan_gateway parameter handlingInspect any router configuration or backup file for parameters related to wan_gateway or genie_fix2.cgi functionality; or observe if the web interface accepts this parameter in network settingsAffected if The router accepts and processes the wan_gateway parameter without visible input validation or sanitization in the web interface
The environment is affected only if the router model is XR300, R7000p, or R6400v2 AND the installed firmware version exactly matches the affected version listed, with the genie_fix2.cgi endpoint accessible via the web interface.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware updates (XR300 v1.0.3.78+, R7000P v1.3.3.154+, R6400v2 1.0.4.128+). If no update available, disable the genie_fix2.cgi functionality or restrict administrative interface access to trusted networks.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51021 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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