Improper AuthenticationWeakness · CWE-287

CVE-2025-60772

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-21
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
Improper authentication in the web-based management interface of NETLINK HG322G V1.0.00-231017, allows a remote unauthenticated attacker to escalate privileges and lock out the legitimate administrator via crafted HTTP requests.

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

The NETLINK HG322G router firmware (V1.0.00-231017) has improper authentication enforcement in its web-based management interface, allowing unauthenticated remote attackers to send crafted HTTP requests that bypass authentication checks, escalate privileges to administrative level, and lock out the legitimate administrator from the device.

MitigationIf vendor firmware update is available, apply it immediately. If no update exists, disable remote web management access from the internet, restrict management interface to trusted internal IPs only, and monitor for unauthorized access attempts.

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
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 the router model
    Access the router admin panel or check the device label/marketing to confirm the model is NETLINK HG322G
    Affected if The device is a NETLINK HG322G router
  2. Check the installed firmware version
    Log into the router web interface (or check via telnet/SSH if available) and navigate to the firmware/version status page to determine if the version is V1.0.00-231017
    Affected if The firmware version is V1.0.00-231017 or earlier
  3. Verify remote web management is enabled
    Check the router security settings for 'Remote Management', 'Web Management', or 'Remote Administration' options to see if they are enabled and accessible from WAN
    Affected if Remote web management (HTTP/HTTPS on WAN interface) is enabled and accessible from untrusted networks
  4. Test authentication bypass
    Send a crafted HTTP request to the router management interface from an untrusted network (or outside the local subnet) without valid credentials, observing if administrative actions succeed without authentication
    Affected if HTTP requests to the management interface succeed without authentication and allow administrative actions
  5. Check for unauthorized admin accounts
    Log into the router (if still accessible) and review the user/account management page for any unknown or unexpected administrator accounts
    Affected if New or unknown administrator accounts appear in the router configuration

A user is affected if they have a NETLINK HG322G router running firmware V1.0.00-231017 with remote web management enabled, allowing unauthenticated access to the admin interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If vendor firmware update is available, apply it immediately. If no update exists, disable remote web management access from the internet, restrict management interface to trusted internal IPs only, and monitor for unauthorized access attempts.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60772 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