CVE-2024-4960
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 classified as critical has been found in D-Link DAR-7000-40 V31R02B1413C. Affected is an unknown function of the file interface/sysmanage/licenseauthorization.php. The manipulation of the argument file_upload leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-264528. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately 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 confidenceUnrestricted file upload vulnerability in D-Link DAR-7000-40's licenseauthorization.php script. Attackers can upload arbitrary files via the file_upload parameter, likely enabling remote code execution. The 9.8 CVSS indicates trivial exploitation with maximum impact.
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= v31r02b1413cCVSS 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.
-
Identify the device modelAccess the device web interface or check the device label/documentation to confirm it is a D-Link DAR-7000-40 deviceAffected if The device is a D-Link DAR-7000-40
-
Check the firmware versionLog into the device admin interface and navigate to the status or system information page to view the installed firmware version. Alternatively, check the device startup logs or firmware file metadataAffected if The firmware version is v31r02b1413c
-
Verify the vulnerable script existsAttempt to access the licenseauthorization.php script via HTTP/HTTPS (e.g., https://<device-ip>/licenseauthorization.php)Affected if The script is accessible and returns a response (200 OK)
-
Confirm file upload functionality is presentInspect the page source of licenseauthorization.php or check if the file_upload parameter is accepted by submitting a test request with a benign fileAffected if The script accepts the file_upload parameter and does not reject the upload
-
Check for unexpected uploaded filesInspect the web root directory on the device (if accessible via SSH/TFTP) or check the upload directory for any unexpected files that were not intentionally uploaded by administratorsAffected if There are unexpected or unknown files in the upload directory
You are affected if you have a D-Link DAR-7000-40 device running firmware v31r02b1413c with the licenseauthorization.php script accessible on the network.
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.
dbcve · scopedProduct is end-of-life with no vendor patch available. Recommend immediate network isolation via firewall/ACLs restricting access to the admin interface, followed by retirement and migration to a supported solution.
- This vulnerability affects D-Link DAR-7000-40 firmware v31r02b1413c, which is explicitly end-of-life and no longer supported by the vendor.
- The vendor (D-Link) has stated the product should be retired and replaced rather than patched.
- Replace the affected D-Link DAR-7000-40 device with a currently supported alternative solution from D-Link or another vendor.
- If immediate replacement is not possible, implement network segmentation to isolate the affected device and restrict access to the management interface from untrusted networks.
- Disable the interface/sysmanage/licenseauthorization.php functionality if possible through network access controls.
- Monitor for any Indicators of Compromise and implement additional logging on the device.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4960 — 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-2024-4960 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