CVE-2023-31814
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 · uneditedD-Link DIR-300 firmware <=REVA1.06 and <=REVB2.06 is vulnerable to File inclusion via /model/__lang_msg.php.
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 · moderate confidenceD-Link DIR-300 router firmware versions REVA1.06 and below, and REVB2.06 and below, contains a file inclusion vulnerability in /model/__lang_msg.php. This allows unauthenticated remote attackers to include arbitrary files from the device's filesystem, potentially leading to sensitive information disclosure or 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<= 1.06<= 2.06CVSS 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 router web interface and check the device information page, or query the device's HTTP headers and response for 'DIR-300' identificationAffected if The device is not a D-Link DIR-300 router
-
Determine the firmware versionLog into the router web interface and navigate to the Status or System Information page to view the firmware version, or use HTTP requests to retrieve version information from the deviceAffected if Firmware version is REVA 1.06 or below, or REVB 2.06 or below
-
Verify the vulnerable script existsSend an HTTP GET request to http://[device-ip]/model/__lang_msg.php and check if the page responds (even with an error)Affected if The script responds, indicating it exists on the device
-
Confirm file inclusion is possibleAttempt to include a known local file such as /etc/passwd or /etc/shadow via the lang parameter: http://[device-ip]/model/__lang_msg.php?lang=../../../../etc/passwdAffected if The response contains contents from the requested file, confirming the vulnerability is present and exploitable
A user is affected if they have a D-Link DIR-300 router running firmware REVA version 1.06 or below, or REVB version 2.06 or below, and the vulnerable /model/__lang_msg.php script is accessible on their 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.
From vendor dataUpdate the firmware to a patched version if available from D-Link. If no patch exists, restrict network exposure to the device, disable PHP remote file inclusion features, and consider network segmentation to limit attack surface.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31814 — 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-31814 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