dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-7715

MEDIUM · 6.3 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20240812. It has been classified as critical. This affects the function sprintf of the file /cgi-bin/photocenter_mgr.cgi. The manipulation of the argument filter leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed that the product is end-of-life. It should be retired and replaced.

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 NAS devices (multiple models including DNS-320, DNS-325, DNS-327L, etc.) allows remote attackers to execute arbitrary commands via the 'filter' parameter in /cgi-bin/photocenter_mgr.cgi. The sprintf function uses unsanitized user input, enabling shell command injection.

MitigationProducts are end-of-life and unsupported; D-Link advises retirement and replacement. Immediately disconnect affected devices from the internet and segregate on internal networks if continued use is required. There will be no vendor patch.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 D-Link NAS model
    Check the device label, admin web interface footer, or system info page for the exact model number (e.g., DNS-320, DNS-325, DNS-327L)
    Affected if Model matches DNS-320, DNS-325, DNS-327L, or other related D-Link NAS models from the same era
  2. Verify photocenter_mgr.cgi exists
    Attempt to access http://<device-ip>/cgi-bin/photocenter_mgr.cgi via HTTP request or check file system if SSH/telnet access is available
    Affected if The CGI script is present and responds to requests (indicates the photo center feature is installed)
  3. Check firmware version
    In the device web UI, navigate to System > Firmware Upgrade or System > Status to view the installed firmware version number
    Affected if Firmware version is any version on these legacy D-Link NAS devices (the vulnerability exists in the shipped code)
  4. Assess network exposure
    Check router/firewall rules to determine if the device's web interface (ports 80/443) is accessible from the internet or untrusted networks
    Affected if The device admin interface is exposed directly to the internet or to untrusted guest networks

The environment is affected if it runs a D-Link DNS-320, DNS-325, DNS-327L or similar NAS model with the photocenter_mgr.cgi accessible and the device is network-accessible to attackers.

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

Products are end-of-life and unsupported; D-Link advises retirement and replacement. Immediately disconnect affected devices from the internet and segregate on internal networks if continued use is required. There will be no vendor patch.

Recommended fix High confidence
  1. These D-Link products (DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05, DNS-1550-04) are end-of-life and no longer supported by the vendor.
  2. The official description explicitly states the products should be retired and replaced.
  3. If these devices must remain in operation, isolate them on a restricted network segment with firewall rules limiting access to trusted IP addresses only.
  4. Consider migrating data and services to actively maintained storage solutions from vendors that provide security updates.
Caveat Products are end-of-life with no available firmware updates; replacement with actively supported hardware is the only complete remediation

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA4.0 h
48.0 hours of engineering $8,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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