dbcve.org
D View 8Application · Dlink

CVE-2023-44412

HIGH · 8.2 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
High EPSS 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
D-Link D-View addDv7Probe XML External Entity Processing Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of D-Link D-View. Authentication is not required to exploit this vulnerability. The specific flaw exists within the addDv7Probe function. Due to the improper restriction of XML External Entity (XXE) references, a crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this vulnerability to disclose information in the context of SYSTEM. Was ZDI-CAN-19571.

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 confidence

This is an XML External Entity (XXE) injection vulnerability in D-Link D-View's addDv7Probe function. The application's XML parser does not properly restrict external entity references, allowing an unauthenticated remote attacker to craft malicious XML documents that can access local files or internal system resources by referencing external URIs.

MitigationDisable XML external entity (XXE) processing in the XML parser configuration, or apply vendor-supplied patches for D-Link D-View. If a patch is unavailable, implement XML input validation and disable external entity resolution.

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
D View 8Application
Affected:= 1.0.2.13

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

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

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 D-Link D-View version
    Locate the installed version of D-Link D-View 8 in the system information or about page. Common locations include the web interface header, help menu, or installation directory readme files.
    Affected if The installed version is exactly 1.0.2.13
  2. Verify addDv7Probe function exists
    Inspect the D-View web application or API endpoints to confirm the addDv7Probe function is present. This may be found in the network probe configuration module or through endpoint enumeration.
    Affected if The addDv7Probe function is present and exposed in the application
  3. Confirm XML processing is enabled
    Check if the application processes XML input through the addDv7Probe or related probe configuration features. This can be verified by reviewing the application's feature set or attempting a benign XML submission to the affected endpoint.
    Affected if XML input processing is enabled for the addDv7Probe function
  4. Inspect XML parser configuration
    Review the application's XML parser settings to determine whether external entity resolution is permitted. This may require access to configuration files or testing the parser behavior with a crafted XML document containing an external entity reference.
    Affected if The XML parser allows external entity references (XXE) or has not been configured to disable them

You are affected if running D-Link D-View 8 version 1.0.2.13 with the addDv7Probe function exposed and the XML parser configured to allow external entity references.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable XML external entity (XXE) processing in the XML parser configuration, or apply vendor-supplied patches for D-Link D-View. If a patch is unavailable, implement XML input validation and disable external entity resolution.

Fix this in D View 8 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44412 — 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-2023-44412 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