Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-118579 – Hidden Backdoor / Unauthenticated Access – D-Link DIR-505 firmware 1.10B02

Be the first to know when new zero-days emerge:

Summary

CVE-2026-118579 is a backdoor vulnerability (CWE-912) in the web management CGI of the D-Link DIR-505 router, firmware 1.10B02. A hidden route lets a remote, unauthenticated attacker bypass authentication and start a service on the device. The CVE record rates it Critical (CVSS v4.0 score 9.3), and a public proof of concept is available.

Technical details

  • Root cause: The web management CGI contains a hidden route, /secmark1524.cgi (function main), with a hardcoded verification branch. It accepts fixed, embedded credential-like values and skips normal authentication.
  • Trigger conditions: According to the public PoC writeup, an attacker sends a POST request to /secmark1524.cgi with five hardcoded form fields (accu, pass, code, hash, cmds). The cmds field is the base64 encoding of tftpd. The attacker needs network access to the web management interface (TCP/80).
  • Attack vector: Network, with no authentication and no user interaction.
  • Impact: A valid request launches an unauthenticated TFTP daemon running as root. The PoC writeup reports that this allows arbitrary file reads as root, for example /etc/shadow and configuration files, over UDP/69. The writeup also describes possible further exploitation through the TFTP upload path. That further claim comes from the public researcher advisory only, and the CVE record does not confirm it.

Affected software

  • D-Link DIR-505 firmware 1.10B02

Severity

  • CVSS v4.0: 9.3 (Critical), CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
  • CVSS v3.1 as listed in the CVE record: 9.8 (Critical), CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R

Mitigation and recommended actions

  • Immediate: I found no D-Link patch or security advisory for this issue. Check D-Link’s support and legacy product pages for the DIR-505 and apply any fixed firmware if one is published.
  • Workarounds: Do not expose the router’s web management interface (TCP/80) to the internet or to untrusted networks. Disable remote administration. Block inbound UDP/69 (TFTP) to the device. Restrict management access to trusted hosts only.
  • Longer term: If no fix is released, consider replacing the device with a supported model.
  • Monitoring: Look for POST requests to /secmark1524.cgi and for unexpected TFTP (UDP/69) activity on or to the router.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge