dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-25246

HIGH · 8.1 CVSS v3.1 Published 2025-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
NETGEAR XR1000 before 1.0.0.74, XR1000v2 before 1.1.0.22, and XR500 before 2.3.2.134 allow remote code execution by unauthenticated users.

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

This vulnerability in NETGEAR XR1000, XR1000v2, and XR500 routers allows unauthenticated remote attackers to execute arbitrary code on affected devices. The flaw exists in firmware versions prior to the specified patches (XR1000 < 1.0.0.74, XR1000v2 < 1.1.0.22, XR500 < 2.3.2.134) and can be exploited without any authentication credentials.

MitigationApply the latest firmware updates from NETGEAR for the affected router models. If updating is not immediately possible, restrict network access to the router's management interface from untrusted networks.

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

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

CVSS:3.1/AV:N/AC:H/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 the NETGEAR router model
    Log into the router's web administration interface (typically at 192.168.1.1) and locate the model number displayed on the dashboard or in the 'Advanced' > 'Administration' > 'Router Status' section. Alternatively, check the physical label on the router device itself.
    Affected if The model is XR1000, XR1000v2, or XR500
  2. Locate the firmware version in the router interface
    In the router's web admin panel, navigate to 'Advanced' > 'Administration' > 'Router Status' or 'Firmware Update' section. The current firmware version is displayed there.
    Affected if A firmware version is displayed and can be read
  3. Compare the XR1000 firmware version against the affected range
    If the router model is XR1000, compare the displayed firmware version (e.g., 1.0.0.x) to 1.0.0.74. Versions lower than 1.0.0.74 are affected.
    Affected if The installed firmware version is lower than 1.0.0.74 (for example, 1.0.0.50 or 1.0.0.72)
  4. Compare the XR1000v2 firmware version against the affected range
    If the router model is XR1000v2, compare the displayed firmware version to 1.1.0.22. Versions lower than 1.1.0.22 are affected.
    Affected if The installed firmware version is lower than 1.1.0.22 (for example, 1.1.0.10 or 1.0.0.74)
  5. Compare the XR500 firmware version against the affected range
    If the router model is XR500, compare the displayed firmware version to 2.3.2.134. Versions lower than 2.3.2.134 are affected.
    Affected if The installed firmware version is lower than 2.3.2.134 (for example, 2.3.2.100 or 2.3.1.50)

You are affected if you have a NETGEAR XR1000, XR1000v2, or XR500 router running firmware version lower than 1.0.0.74, 1.1.0.22, or 2.3.2.134 respectively.

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 the latest firmware updates from NETGEAR for the affected router models. If updating is not immediately possible, restrict network access to the router's management interface from untrusted networks.

Recommended fix High confidence

XR1000: upgrade to 1.0.0.74 or later; XR1000v2: upgrade to 1.1.0.22 or later; XR500: upgrade to 2.3.2.134 or later

  1. 1. Identify your NETGEAR router model (XR1000, XR1000v2, or XR500) from the device label or web interface
  2. 2. Current firmware version can be found in the web administration interface under 'Administration' > 'Firmware Update' or 'Advanced' > 'Administration' > 'Router Update'
  3. 3. Download the appropriate fixed firmware from the official NETGEAR support website (support.netgear.com) for your specific model
  4. 4. For XR1000: Download firmware version 1.0.0.74 or later
  5. 5. For XR1000v2: Download firmware version 1.1.0.22 or later
  6. 6. For XR500: Download firmware version 2.3.2.134 or later
  7. 7. In the router web interface, navigate to the firmware update section
  8. 8. Click 'Browse' or 'Choose File' and select the downloaded firmware file
Caveat Standard firmware update; ensure backup of router configuration before upgrading; some settings may reset to defaults requiring reconfiguration

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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