dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-57595

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-27
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
DLINK DIR-825 REVB 2.03 devices have an OS command injection vulnerability in the CGl interface apc_client_pin.cgi, which allows remote attackers to execute arbitrary commands via the parameter "wps_pin" passed to the apc_client_pin.cgi binary through a POST request.

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

This is an OS command injection vulnerability in the D-Link DIR-825 REVB router firmware. The web interface CGI binary apc_client_pin.cgi fails to sanitize user input from the 'wps_pin' parameter in POST requests, allowing attackers to inject and execute arbitrary operating system commands on the device.

MitigationApply any available vendor firmware update; if no patch exists, isolate the device behind a firewall or consider replacement, and disable WPS functionality as a compensating control.

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. Confirm device model is DIR-825 REVB
    Locate the device label or access the router admin interface (typically at 192.168.0.1) and check the model number displayed in the status or system settings area
    Affected if The device is a D-Link DIR-825 REVB router
  2. Verify web interface is accessible
    Attempt to reach the router web interface over HTTP/HTTPS on the local network (commonly port 80 or 443)
    Affected if The router web management interface is exposed and accessible
  3. Confirm apc_client_pin.cgi endpoint exists
    Check if the CGI binary exists by attempting a POST request to http://[router-ip]/cgi-bin/apc_client_pin.cgi or inspecting the web server's CGI directory if accessible
    Affected if The apc_client_pin.cgi script is present on the device web server
  4. Check if WPS functionality is enabled
    Access the router admin interface and navigate to the WPS settings page (usually under Wireless or Advanced settings) to determine if Wi-Fi Protected Setup is turned on
    Affected if WPS is enabled and the wps_pin parameter can be submitted to the vulnerable CGI script
  5. Verify firmware version
    In the router admin interface, go to the Firmware or Status page to view the installed firmware version number
    Affected if The installed firmware version has not been patched to address the command injection flaw in the wps_pin parameter processing

A user is affected if they own a D-Link DIR-825 REVB router with the web interface accessible, the vulnerable apc_client_pin.cgi script present, WPS enabled, and an unpatched firmware version.

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

Apply any available vendor firmware update; if no patch exists, isolate the device behind a firewall or consider replacement, and disable WPS functionality as a compensating control.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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