CVE-2025-59369
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 · uneditedA SQL injection vulnerability has been identified in bwdpi. A remote, authenticated attacker could leverage this vulnerability to potentially execute arbitrary SQL queries, leading to unauthorized data access. Refer to the 'Security Update for ASUS Router Firmware' 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 confidenceSQL injection vulnerability in the bwdpi component of ASUS router firmware allows authenticated remote attackers to execute arbitrary SQL queries, potentially exposing sensitive data from the device's database.
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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the bwdpi service statusAccess the router's web interface or use SSH to check if the bwdpi service is running. Look for processes related to bwdpi or bandwidth monitoring features.Affected if The bwdpi component is present and running on the device
-
Determine the router firmware versionLog into the ASUS router admin interface and navigate to the Administration > Firmware Upgrade section, or use the command line to retrieve the firmware version (e.g., cat /etc/version).Affected if The installed firmware version falls within the vulnerable version range for CVE-2025-59369
-
Verify remote management access to bwdpiCheck the router's management settings to determine if the bwdpi interface is accessible from external networks. Look for settings related to Remote Management, WAN access, or the bwdpi-specific management port.Affected if Remote access to the bwdpi management interface is enabled and exposed to untrusted networks
-
Confirm authentication configurationReview the user accounts and authentication settings for the router, particularly those associated with the bwdpi or bandwidth monitoring features.Affected if Weak or default credentials are in use, or the bwdpi interface is accessible without proper authentication enforcement
-
Inspect network exposure of the bwdpi portPerform a port scan from outside the local network to identify if the bwdpi management port (commonly associated with the ASUS router admin interface) is exposed to the WAN.Affected if The bwdpi management port is reachable from external networks without VPN or IP restriction
A user is affected if their ASUS router has the bwdpi component enabled, is running a firmware version within the vulnerable range, and the bwdpi interface is accessible remotely with authentication that can be exploited.
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 the official ASUS firmware security update referenced in the ASUS Security Advisory. If unable to patch immediately, restrict access to the bwdpi management interface to trusted networks and ensure strong authentication credentials are in place.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59369 — 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-59369 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