What it is
CVE-2024-0769 is an unauthenticated D-Link DIR-859 HTTP POST Request hedwig.cgi path traversal. ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DIR-859 1.06B01. It has been rated as critical....
Vulnerability report
D-Link DIR-859 HTTP POST Request hedwig.cgi path traversal
D-Link / DIR-859 · 1.06b01
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2024-0769 is an unauthenticated D-Link DIR-859 HTTP POST Request hedwig.cgi path traversal. ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DIR-859 1.06B01. It has been rated as critical....
Is it exploited?
Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV. Also confirmed by third-party sources.
Who is affected?
D-Link / DIR-859 1.06b01.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DIR-859 1.06B01. It has been rated as critical. Affected by this issue is some unknown functionality of the file /hedwig.cgi of the component HTTP POST Request Handler. The manipulation of the argument service with the input ../../../../htdocs/webinc/getcfg/DHCPS6.BRIDGE-1.xml leads to path traversal. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-251666 is the identifier assigned to this vulnerability. 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. Eine kritische Schwachstelle wurde in D-Link DIR-859 1.06B01 ausgemacht. Es geht hierbei um eine nicht näher spezifizierte Funktion der Datei /hedwig.cgi der Komponente HTTP POST Request Handler. Durch Manipulieren des Arguments service mit der Eingabe ../../../../htdocs/webinc/getcfg/DHCPS6.BRIDGE-1.xml mit unbekannten Daten kann eine path traversal-Schwachstelle ausgenutzt werden. Der Angriff kann über das Netzwerk angegangen werden. Der Exploit steht zur öffentlichen Verfügung.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CVE
A trusted third party reported exploitation.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CVE First | 2026-06-01 10:34 UTC |
| CISA | 2026-06-02 14:07 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
82.7%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
AV:N/AC:L/Au:N/C:P/I:N/A:N
Timeline
14:07 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
10:34 UTC
High-confidence, third-party attested exploitation
08:00 UTC
Vulnerability disclosed publicly
15:12 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2024-0769
Free JSON includes basic KEV fields{
"cve_id": "CVE-2024-0769",
"confidence": "Confirmed",
"cvss_score": 5.3,
"cvss_estimated": false,
"epss_score": 0.82714,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}