CVE-2023-5143
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, which was classified as critical, has been found in D-Link DAR-7000 up to 20151231. This issue affects some unknown processing of the file /log/webmailattach.php. The manipulation of the argument table_name leads to an unknown weakness. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-240239. 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 confidenceSQL injection vulnerability in D-Link DAR-7000 device management software. The /log/webmailattach.php script does not properly sanitize the table_name parameter, allowing remote attackers to inject arbitrary SQL commands. The vulnerability has a CVSS score of 9.8 (Critical) and a public exploit is available.
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<= 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
- 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.
-
Confirm the device modelIdentify if the target device is a D-Link DAR-7000. Check the device physical label, admin interface, or network scan results for the model identifier.Affected if The device is confirmed to be a D-Link DAR-7000 unit
-
Check the firmware versionLog into the device management interface and navigate to the system or firmware information page to find the firmware build date. Compare this against the affected version range.Affected if The firmware build date is 20151231 or earlier (this is the last vulnerable version)
-
Locate the vulnerable scriptAttempt to access the /log/webmailattach.php file via HTTP from the device. Use a browser or curl command: curl http://TARGET_IP/log/webmailattach.phpAffected if The web server responds to requests for /log/webmailattach.php (a 404 does not necessarily mean unaffected if the path differs)
The device is affected if it is a D-Link DAR-7000 running firmware version 20151231 or earlier AND the /log/webmailattach.php endpoint is 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 · scopedThis product is end-of-life and no longer supported by the vendor. The vendor recommends retiring and replacing the device rather than applying patches. Immediate network isolation or WAF rules should be deployed as temporary mitigations while planning replacement.
- This vulnerability affects D-Link DAR-7000 firmware version 20151231 and earlier.
- D-Link has confirmed this product is end-of-life (EOL) and no longer supported by the maintainer.
- The vendor explicitly recommends retiring and replacing this product rather than applying patches.
- If continued use is unavoidable, isolate the device on a restricted network segment to minimize attack surface.
- Implement network-level access controls (firewall rules, ACLs) to limit connectivity to the affected system from untrusted sources.
- Monitor for indicators of compromise given the public exploit availability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.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 $13,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5143 — 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-5143 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