How severe is CVE-2019-20499?

CVE-2019-20499 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-20499?

Affected package information for CVE-2019-20499 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-20499?

No fixed version has been published for CVE-2019-20499 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2019-20499 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2019-20499, including 2 documented proof-of-concept exploits on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-20499?

CVE-2019-20499 has an EPSS (Exploit Prediction Scoring System) score of 96.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2019-20499?

CVE-2019-20499 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2019-20499?

CVE-2019-20499 affects dlink dwl-2600ap firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2019-20499 published, and has it been updated?

CVE-2019-20499 was published on March 5, 2020 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2019-20499

HIGH

D-Link DWL-2600AP 4.2.0.15 Rev A devices have an authenticated OS command injection vulnerability via the Restore Configuration functionality in the Web interface, using shell metacharacters…

Published

Mar 5, 2020

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

96.6%probability of exploitation in next 30 days

Very High Risk100th percentile+7.79%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

D-Link DWL-2600AP 4.2.0.15 Rev A devices have an authenticated OS command injection vulnerability via the Restore Configuration functionality in the Web interface, using shell metacharacters in the admin.cgi?action=config_restore configRestore or configServerip parameter.

Affected Products

1 product · 1 configurations

dwl-2600ap firmwaredlink

≤ 4.2.0.15

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-48274remotehardware✓ Verified

DLINK DWL-2600 - Authenticated Remote Command Injection (Metasploit)

by Metasploit · Mar 31, 2020

Exploit-DB Source

EDB-46841webappshardware

D-Link DWL-2600AP - Multiple OS Command Injection

by Raki Ben Hamouda · May 14, 2019

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-20499 in your stack?

O3 detects CVE-2019-20499 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works