dbcve.org
Jwnr2000v2 FirmwareOperating system · Netgear

CVE-2025-4122

HIGH · 8.8 CVSS v3.1 Published 2025-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability was found in Netgear JWNR2000v2 1.0.0.11. It has been rated as critical. Affected by this issue is the function sub_435E04. The manipulation of the argument host leads to command injection. The attack may be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

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 command injection vulnerability exists in the sub_435E04 function of the Netgear JWNR2000v2 router firmware (v1.0.0.11). The 'host' parameter passed to this function is not properly sanitized before being used in a system call, allowing an unauthenticated remote attacker to inject and execute arbitrary shell commands on the device.

MitigationReplace the end-of-life Netgear JWNR2000v2 router with a currently supported model, as the vendor did not respond to early disclosure. If replacement is impossible, restrict all external access to the router's web management interface via firewall rules or disable remote management.

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
Jwnr2000v2 FirmwareOperating system
Affected:= 1.0.0.11

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

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Locate the device label or check the router's web management interface for the model number. Confirm it is a Netgear JWNR2000v2.
    Affected if The device is not a Netgear JWNR2000v2 router.
  2. Check the installed firmware version
    Access the router's web management interface (typically at 192.168.1.1) and navigate to the firmware version or status page. Alternatively, check the firmware file if you have local access to the firmware image.
    Affected if The firmware version is 1.0.0.11.
  3. Verify web management interface accessibility
    Attempt to access the router's web interface from the network. Determine if HTTP/HTTPS ports (80/443) are listening and reachable from your testing location.
    Affected if The web management interface is accessible over the network.
  4. Check if remote management is enabled
    In the router's web management interface, locate the remote management or administration settings (usually under Advanced > Admin > Remote Management). Determine if remote access is enabled.
    Affected if Remote management is enabled and the web interface is externally accessible.

You are affected if you have a Netgear JWNR2000v2 router running firmware version 1.0.0.11 with its web management interface accessible from the network.

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

Replace the end-of-life Netgear JWNR2000v2 router with a currently supported model, as the vendor did not respond to early disclosure. If replacement is impossible, restrict all external access to the router's web management interface via firewall rules or disable remote management.

Recommended fix Moderate confidence

Latest available firmware version for JWNR2000v2 from Netgear support (check www.netgear.com/support for current version)

  1. 1. Check Netgear's support website (www.netgear.com/support) for the latest firmware version for the JWNR2000v2 router
  2. 2. Download the most recent firmware version available from the official Netgear support page
  3. 3. Access the router's web administration interface by entering the router's IP address (commonly 192.168.1.1) in a web browser
  4. 4. Navigate to the Administration or Advanced settings section
  5. 5. Look for a Firmware Update or Router Upgrade option
  6. 6. Upload and apply the downloaded firmware file
  7. 7. After the update completes, verify the router is functioning normally
  8. 8. Confirm the new firmware version in the router's admin interface to ensure the update was successful
Caveat Router firmware updates typically require a brief downtime; ensure no critical operations are in progress before upgrading

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

Fix this in Jwnr2000v2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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