CVE-2023-36089
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 · uneditedAuthentication Bypass vulnerability in D-Link DIR-645 firmware version 1.03 allows remote attackers to gain escalated privileges via function phpcgi_main in cgibin. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
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-645 firmware version 1.03 contains an authentication bypass vulnerability in the phpcgi_main function within cgibin. This allows remote, unauthenticated attackers to bypass authentication controls and gain escalated privileges on affected devices.
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.03CVSS 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 firmware versionAccess the device admin interface or check the device label/packaging for the firmware version. If accessing the web interface, look for a 'Status' or 'Firmware' section that displays the current version.Affected if The installed firmware version is exactly 1.03
-
Confirm the device modelVerify that the affected device is specifically the D-Link DIR-645 router. Check the device label or web interface for the exact model number.Affected if The device model is D-Link DIR-645 with firmware version 1.03
-
Check if the web management interface is network-accessibleAttempt to access the device's web interface from a remote network location, or review firewall/network rules to determine if ports 80 or 443 (HTTP/HTTPS) are exposed to untrusted networks.Affected if The cgibin web interface is reachable from untrusted networks (such as the internet) and the firmware is version 1.03
-
Verify remote management settingsLog into the device admin interface and navigate to the management/administration settings to check if 'Remote Management' or 'WAN Management' is enabled.Affected if Remote management access is enabled on a device running firmware version 1.03
A device is affected if it is a D-Link DIR-645 running firmware version 1.03 and its web management interface (cgibin) is accessible from untrusted networks.
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 this product is end-of-life and no longer supported by D-Link, replace affected devices with currently supported models. If immediate replacement is not feasible, isolate affected devices behind a firewall and disable WAN management access to reduce exposure.
- Replace the D-Link DIR-645 device with a currently supported model from D-Link or another vendor, as this device is end-of-life and no longer receives security updates.
- If immediate replacement is not possible, isolate the device on a restricted network segment with firewall rules limiting access to trusted IP addresses only.
- Disable remote management interfaces if not required, restricting access to local network only.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36089 — 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-36089 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