dbcve.org
InjectionWeakness · CWE-74

CVE-2025-11488

HIGH · 7.3 CVSS v3.1 Published 2025-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A weakness has been identified in D-Link DIR-852 up to 20251002. This affects an unknown part of the file /HNAP1/. Executing manipulation can lead to command injection. The attack may be launched remotely. The exploit has been made available to the public and could be exploited. This vulnerability only affects products that are no longer supported by the maintainer.

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

Command injection vulnerability in D-Link DIR-852 routers (firmware up to 20251002) affecting the /HNAP1/ interface. An attacker can execute arbitrary commands on the device remotely without authentication due to insufficient input validation, leading to full device compromise.

MitigationSince D-Link DIR-852 is end-of-life and no longer supported, immediate network isolation is recommended; replace with a currently supported router. If continued use is required, restrict HNAP1 interface access via firewall rules and disable remote management.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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
    Check the device label or access the web interface and look for the model number in the status or system information page
    Affected if The device is not a D-Link DIR-852, then it is not affected by this specific CVE
  2. Check the firmware version
    Access the router web interface, go to Status or System settings, and note the firmware version date. Compare it to 20251002
    Affected if The firmware version date is 20251002 or earlier, meaning the device may have the vulnerability
  3. Verify if the HNAP1 interface is accessible
    Attempt to access http://[router-ip]/HNAP1/ from a browser. A successful connection (any response, even an error) indicates the interface is enabled
    Affected if The HNAP1 interface returns a response (even an error message), confirming it is active and potentially exploitable
  4. Check if remote management is enabled
    In the router web interface, go to Settings > Remote Management or Advanced > Remote Management, and see if 'Enable Remote Management' or similar option is turned on
    Affected if Remote management is enabled and the HNAP1 interface is accessible from WAN, the device is at higher risk of unauthenticated exploitation

A D-Link DIR-852 router with firmware dated 20251002 or earlier that has the HNAP1 interface accessible (especially from WAN) is affected by CVE-2025-11488 and vulnerable to unauthenticated command injection.

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

Since D-Link DIR-852 is end-of-life and no longer supported, immediate network isolation is recommended; replace with a currently supported router. If continued use is required, restrict HNAP1 interface access via firewall rules and disable remote management.

Recommended fix High confidence
  1. Recognize that the D-Link DIR-852 is end-of-life (EOL) and no longer supported by the vendor, meaning no official firmware patch will be released for CVE-2025-11488.
  2. Replace the affected D-Link DIR-852 device with a currently supported router model from D-Link or another vendor that receives regular security updates.
  3. If immediate replacement is not feasible, implement network-level mitigations: configure the router's firewall to block all external access to the /HNAP1/ interface (port 80/443) from the WAN side, or disable remote management entirely if not required.
  4. If the router must remain in service, consider placing it behind a properly configured upstream firewall and limiting its network exposure to minimize the attack surface for this command injection vulnerability.
  5. Document the EOL status and the need for replacement in the organization's asset management and risk acceptance records.
Caveat Replacing the EOL DIR-856 router requires procurement of new hardware and potential network reconfiguration; no direct firmware upgrade path exists as the product is no longer supported.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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