CVE-2026-16332 DNS-320 vulnerability
A vulnerability was detected in D-Link DNS-320 1.0.2. This impacts an unknown function of the file /mydlink/multi_uploadify.php. Performing a manipulation of the argument Filedata[] results in unrestricted upload. The attack is possible to be carried out remotely. The exploit is now public and may be used.
Browse PHP security risksQuick answer
D-Link DNS-320 should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 1.0.2
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-16332 affects DNS-320 and involves unsafe file upload. Successful exploitation may place untrusted files on the server and can lead to data exposure, content changes, or code execution. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. No confirmed patched DNS-320 firmware is recorded. Disable or block multi_uploadify.php, isolate the NAS from the internet, and replace the device if D-Link does not provide a supported fix.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses DNS-320.
- Compare the installed version with the recorded affected range: 1.0.2.
- No confirmed patched DNS-320 firmware is recorded. Disable or block multi_uploadify.php, isolate the NAS from the internet, and replace the device if D-Link does not provide a supported fix.
- Until remediation is complete, remove public management access, isolate affected devices, and allow administration only from a trusted network.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to DNS-320; remove access that is not required.
- Review upload directories, web logs, process activity, and file-integrity alerts for unexpected files, scripts, or execution attempts.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-16332 in place.
- Use a safe regression test to confirm the affected unsafe file upload path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-16332?
D-Link DNS-320 versions listed as affected should be reviewed: 1.0.2.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.