On this page (7 sections)

A newly published record, CVE-2026-129444, describes a hard-coded credentials weakness in the FTP daemon of the D-Link DSL-6740C, version 20131126. The record says the attack can be carried out remotely and that an exploit is publicly available and might be used.

If you manage a DSL-6740C at an office, a branch location or a client site, this is worth checking today. The public information is thin and no fixed firmware is listed, so the practical focus is on reducing exposure.

What was reported

The GitHub Advisory Database entry and the NVD record were both published on November 15, 2026. They say the FTP Daemon component is affected through an unknown function in the file /etc/templates/ftpd/ftpd_conf.php, and that manipulation leads to hard-coded credentials. The NVD text repeats the GitHub text, so this is one report, not two independent confirmations.

The GitHub entry is marked Unreviewed and lists no package, no affected version range beyond the single version named in the description, and no patched version. Its references include a VulDB entry and a third-party repository whose name suggests evidence of default FTP credentials. The research does not describe the contents of those references and we have not verified them, so treat the details of the flaw as reported, not confirmed.

What hard-coded credentials mean in practice

A hard-coded credential is a username and password built into firmware or a configuration template instead of being set by the owner. In general, every device running the same firmware shares that login, and changing an admin password you control does not alter a secret embedded in the software. The research does not say which account the credential belongs to or whether this is true of the DSL-6740C in every detail, so read this as the general weakness class, not a confirmed description of this device.

The CVSS v4 metrics on the GitHub page describe a network attack vector, low complexity, no privileges and no user interaction, with high impact on confidentiality, integrity and availability for both the vulnerable and subsequent systems. In plain terms, if the FTP service is reachable, the reported conditions for an attack are minimal. What an attacker could do after logging in to the FTP daemon is not described in the research, so we will not speculate.

Who is realistically exposed

  • Owners of a D-Link DSL-6740C reporting firmware or version 20131126. Check the device label and the admin page to confirm.
  • Devices where the FTP service is enabled, or where the WAN side exposes services. The research does not say whether FTP is on by default.
  • Small offices and remote sites where a DSL router is the only perimeter device and is rarely reviewed.
  • Hosting and agency teams that inherited routers at client sites without an inventory.

The product appears to be old, and the research does not say whether D-Link still supports it. The advisory references the vendor site (www.dlink.com), so check there for any notice about this model. Do not assume a patch exists.

How to check your exposure

Start with an inventory: confirm the model and firmware version on the device label or admin page. Then check from outside your network whether the FTP port answers. The command below is a read-only connection test using the common netcat tool; run it from a machine outside your network (for example a cloud server), replacing the placeholder with your router's public IP. A successful connection means port 21 is reachable from the internet.

Test whether FTP (port 21) is reachable from outside (run from an external host)Shell
nc -vz -w 5 YOUR_PUBLIC_IP 21

If you collect router logs with syslog, you can also look for FTP-related activity. This grep prints the last 50 FTP-related lines from an exported log file; adjust the file name to your setup. Repeated login attempts from unfamiliar addresses are worth investigating.

Search an exported router or syslog file for FTP activityShell
grep -i ftp router.log | tail -n 50

The free SSL checker and security headers checker cover websites, not routers, so they will not tell you about this issue. A Webforta Scan of a verified site shows what is exposed at the web layer, but it is no substitute for checking the router itself.

What to do now

Caution. Changing router settings or rebooting will briefly interrupt connectivity. Schedule it outside business hours and keep a copy of your current configuration first.
  1. Identify every DSL-6740C you manage and note the firmware version.
  2. Block inbound port 21 at the network edge or in the router's WAN-side firewall rules if it allows that. This is the most dependable step, because it does not rely on a setting this model may or may not offer.
  3. Check the admin interface for an option to turn off the FTP service. The research does not confirm the DSL-6740C offers one, so do not rely on it alone.
  4. Make sure no other remote management or file-sharing service is exposed on the WAN interface.
  5. Restrict any required FTP access to a known management IP address or a VPN.
  6. Look for a firmware notice on the D-Link site. Apply an update only if D-Link publishes one for this model, and download it only from the vendor.
  7. Review the router for unfamiliar users, port forwards or DNS settings, and set a new admin password.
  8. If the device is end of life and no fix appears, plan to replace it with a supported model.
As general reasoning, not a finding about this device: a credential built into firmware may survive a factory reset or a password change, so blocking network access to the service is a safer assumption than relying on resets. The research gives no vendor mitigation guidance for this issue.

Detection and monitoring afterwards

Keep watching for three things: a vendor advisory or firmware release, any report of active exploitation, and changes on your own network. Because the record is Unreviewed and brief, details such as affected version ranges may be updated. Re-check the GitHub advisory and the NVD page periodically.

Treat unexpected outbound traffic from the router, configuration changes and new DNS settings as signs to investigate. If you suspect a compromise, follow our guide on what to do when a website is hacked. For sites behind the router, uptime and DNS monitoring can flag unexpected changes from the outside. For broader guidance, see small business website security.

What we do not know yet

  • Whether D-Link has acknowledged the issue or plans a fix.
  • Whether other firmware versions or D-Link models are affected.
  • Which account the credentials belong to and what access they grant.
  • Whether the DSL-6740C lets owners disable the FTP service.
  • Whether anyone is exploiting the flaw in the wild. The record only says a public exploit exists and might be used.
  • Why the CVE record shows CVSS 10 while the GitHub page shows 9.3 under CVSS v4.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-129444 - GitHub Advisory Databasegithub.com
  2. CVE-2026-129444: A vulnerability was identified in D-Link DSL-6740C 20131126.nvd.nist.gov ·
  • D-Link
  • router security
  • hard-coded credentials
  • CVE-2026-129444
  • FTP