CVE-2025-59367
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 · uneditedAn authentication bypass vulnerability has been identified in certain DSL series routers, may allow remote attackers to gain unauthorized access into the affected system. Refer to the 'Security Update for DSL Series Router' section on the ASUS Security Advisory for more information.
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 confidenceThis is an authentication bypass vulnerability in ASUS DSL series routers that allows remote attackers to circumvent authentication mechanisms and gain unauthorized administrative access to the affected device without valid credentials.
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.1.2.3_1010< 1.1.2.3_1010< 1.1.2.3_1010CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router model and firmware versionLog into the router web interface or use the command line interface (telnet/ssh if enabled) to locate the System Information or Firmware Version page. Typical paths: Administration > Firmware Upgrade or Status > Device Information.Affected if The model is Asus DSL-AC51, DSL-N16, or DSL-AC750 AND the firmware version is earlier than 1.1.2.3_1010.
-
Verify remote management statusIn the router web interface, navigate to WAN > Remote Management or Administration > System > Remote Access. Check if the remote management or Web Access from WAN feature is enabled.Affected if Remote management interfaces are exposed to the WAN (internet), making the device reachable for remote exploitation.
-
Review administrator accountsIn the router web interface, go to Administration > Account or User Management. Review the list of configured administrator accounts for any unfamiliar or unauthorized accounts.Affected if Unexpected additional administrator accounts exist that were not created by the legitimate administrator.
-
Check for active admin sessionsIn the router web interface, look for a Status > Active Sessions, System Log, or Connections table. Identify any active administrative sessions from unexpected IP addresses, particularly WAN IP addresses.Affected if Active administrative sessions are originating from external IP addresses that the administrator does not recognize.
A defender is affected if they own an Asus DSL-AC51, DSL-N16, or DSL-AC750 router running firmware earlier than 1.1.2.3_1010 AND have remote management enabled or notice unauthorized admin activity.
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.
dbcve · scoped1.1.2.3_1010
Apply vendor-supplied firmware updates from ASUS Security Advisory when available; until then, disable remote management interfaces, restrict management access to trusted IP addresses only, and monitor for unauthorized access attempts.
1.1.2.3_1010
- 1. Identify your specific ASUS DSL router model (DSL-AC51, DSL-N16, or DSL-AC750)
- 2. Navigate to the ASUS support website and locate the firmware download page for your specific model
- 3. Download the firmware version 1.1.2.3_1010 or later from the official ASUS support page
- 4. Access the router's web administration interface
- 5. Navigate to the Administration > Firmware Upgrade section
- 6. Upload the downloaded firmware file and wait for the upgrade process to complete
- 7. After the router restarts, verify the firmware version has been updated to 1.1.2.3_1010 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59367 — 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-2025-59367 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