CVE-2025-60854
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 vulnerability has been found in D-Link R15 (AX1500) 1.20.01 and below. By manipulating the model name parameter during a password change request in the web administrator page, it is possible to trigger a command injection in httpd.
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 confidenceA command injection vulnerability exists in D-Link R15 (AX1500) router firmware 1.20.01 and below. The vulnerability is in the web administrative interface (httpd) where the model name parameter can be manipulated during a password change request to inject and execute arbitrary operating system commands. This is a pre-authentication flaw allowing unauthenticated attackers to achieve remote code execution with root privileges on the affected device.
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.20.01CVSS 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.
-
Confirm device is D-Link R15Check the router label or access the web interface and locate the model number in the status or system information pageAffected if The device model displays as R15 or AX1500
-
Identify firmware versionAccess the router's web administrative interface and navigate to the firmware or system settings page to view the installed firmware versionAffected if The firmware version is 1.20.01 or lower
-
Verify httpd service is runningAttempt to access the router's web interface via HTTP or HTTPS on the device's IP addressAffected if The web administrative interface responds to requests
-
Assess network exposure of admin interfaceCheck the router's firewall or port forwarding settings to determine if the web management port is exposed to WAN or untrusted networksAffected if The administrative web interface is accessible from outside the trusted local network
A defender is affected if they have a D-Link R15 router running firmware version 1.20.01 or below with the httpd service accessible, since the pre-authentication command injection can be exploited by any network attacker who can reach the web interface.
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 dataRestrict access to the router's web admin interface to trusted networks only; avoid exposing it to the internet. If no firmware update is available from D-Link, consider replacing the device with a supported model.
- Consultation6.0 h
- Implementation30.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60854 — 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-60854 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