dbcve.org
Dir 816 FirmwareOperating system · Dlink

CVE-2024-13107

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
A vulnerability was found in D-Link DIR-816 A2 1.10CNB05_R1B011D88210. It has been classified as critical. This affects an unknown part of the file /goform/form2LocalAclEditcfg.cgi of the component ACL Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

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 confidence

D-Link DIR-816 A2 router firmware 1.10CNB05_R1B011D88210 contains an improper access control vulnerability in the ACL Handler component (/goform/form2LocalAclEditcfg.cgi). The vulnerability allows remote attackers to bypass access controls and modify Access Control List configurations without proper authentication or authorization, likely due to missing or inadequate session validation in the ACL edit CGI endpoint.

MitigationApply any available firmware update from D-Link; if unavailable, disable remote management via WAN interface, restrict administrative access to trusted IPs, and consider network segmentation to limit exposure.

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
Dir 816 FirmwareOperating system
Affected:= 1.10cnb05_r1b011d88210

CVSS 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router web interface or check the device label to confirm it is a D-Link DIR-816 A2 model.
    Affected if The device is NOT a D-Link DIR-816 A2 router.
  2. Check the installed firmware version
    Log into the router web interface and navigate to the Status or System section to view the firmware version, or use the command line if available. Compare against 1.10CNB05_R1B011D88210.
    Affected if The firmware version IS exactly 1.10CNB05_R1B011D88210.
  3. Verify the vulnerable CGI endpoint exists
    Attempt to access the URL /goform/form2LocalAclEditcfg.cgi on the router (e.g., http://router-ip/goform/form2LocalAclEditcfg.cgi). Check if the endpoint responds or returns any ACL-related content.
    Affected if The endpoint is accessible and returns a response (indicating the vulnerable component is present).
  4. Check if WAN/remote management is enabled
    In the router web interface, go to the Advanced or Administration settings and check if Remote Management or Web Access from WAN is enabled.
    Affected if Remote management over WAN is enabled, allowing external attackers to reach the vulnerable endpoint.

You are affected if you have a D-Link DIR-816 A2 router running firmware version 1.10CNB05_R1B011D88210 with the vulnerable /goform/form2LocalAclEditcfg.cgi endpoint accessible, especially from the WAN interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available firmware update from D-Link; if unavailable, disable remote management via WAN interface, restrict administrative access to trusted IPs, and consider network segmentation to limit exposure.

Recommended fix Moderate confidence

Latest available DIR-816 A2 firmware from D-Link support website

  1. 1. Visit the official D-Link support website at www.dlink.com to check for available firmware updates for the DIR-816 A2 model.
  2. 2. Navigate to the product support page for DIR-816 A2 and locate the firmware downloads section.
  3. 3. Download the latest available firmware version for your device.
  4. 4. Access the router's web management interface (typically at 192.168.0.1).
  5. 5. Navigate to the Administration or System settings menu.
  6. 6. Select the firmware upgrade option and upload the downloaded firmware file.
  7. 7. Wait for the upgrade process to complete - do not power off the device during this process.
  8. 8. After reboot, verify the new firmware version is installed by checking the system status page.
Caveat Router firmware upgrades may reset configuration to defaults; backup current settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 816 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13107 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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