CVE-2023-5145
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 has been found in D-Link DAR-7000 up to 20151231 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /sysmanage/licence.php. The manipulation of the argument file_upload leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-240241 was assigned to this vulnerability. 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 (end-of-life) allows remote attackers to upload arbitrary files via the file_upload parameter in /sysmanage/licence.php, potentially leading to remote code execution.
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<= 20151231<= 20151231CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 D-Link device modelAccess the device administrative interface or check the physical device label to confirm the model is a DAR-7000 or DAR-8000 series device.Affected if The device is a D-Link DAR-7000 or DAR-8000.
-
Check the firmware versionLocate the firmware version in the device administrative interface (typically under System, Status, or About sections) or via CLI if accessible. Compare the version date or number against 20151231.Affected if The firmware version date is 20151231 or earlier.
-
Verify the /sysmanage/licence.php endpoint is accessibleAttempt to access https://<device-ip>/sysmanage/licence.php from a system that can reach the device. A successful HTTP response (even an error page) indicates the endpoint exists.Affected if The endpoint returns an HTTP response rather than a connection failure.
-
Confirm management interface is network-exposedDetermine if the device management interface (typically ports 80, 443, or custom admin ports) is accessible from network segments beyond the intended administrative zone.Affected if The management interface is reachable from networks other than a dedicated admin VLAN.
The environment is affected if the device is a D-Link DAR-7000 or DAR-8000 running firmware dated 20151231 or earlier, with the management interface network-accessible.
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 · scopedSince the product is end-of-life and unsupported, the official guidance is to retire and replace the device. If continued use is unavoidable, consider network isolation and disable the affected service, but replacement is strongly recommended.
- This vulnerability affects D-Link DAR-7000 and DAR-8000 devices which are end-of-life and no longer supported by the vendor.
- The official description explicitly states: 'It should be retired and replaced.'
- Replace the affected D-Link DAR-7000/DAR-8000 devices with a currently supported alternative product.
- If replacement is not immediately possible, implement network segmentation to isolate these devices and restrict access to the /sysmanage/licence.php endpoint using firewall rules or ACLs.
- Monitor for any unauthorized file uploads or suspicious activity on these devices.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5145 — 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-2023-5145 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