CVE-2013-7471 in the critical feed json
An issue was discovered in soap.cgi?service=WANIPConn1 on D-Link DIR-845 before v1.02b03, DIR-600 before v2.17b01, DIR-645 before v1.04b11,…
published 7y ago modified 4mo ago also EUVD-2013-7229
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 24.6%
- EPSS 24.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
An issue was discovered in soap.cgi?service=WANIPConn1 on D-Link DIR-845 before v1.02b03, DIR-600 before v2.17b01, DIR-645 before v1.04b11, DIR-300 rev. B, and DIR-865 devices. There is Command Injection via shell metacharacters in the NewInternalClient, NewExternalPort, or NewInternalPort element of a SOAP POST request.
Patch / fix
- dlink dir-600_firmware 2.17b01
- dlink dir-645_firmware 1.04b11
- dlink dir-845_firmware 1.02b03
Is CVE-2013-7471 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
24.59% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- s3cur1ty.de http://www.s3cur1ty.de/m1adv2013-020 referenced PoC, tagged "exploit" by a source, unverified
- exploit-db.com https://www.exploit-db.com/exploits/27044 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-77 Improper Neutralization of Special Elements used in a Command
References
-
s3cur1ty.de
/m1adv2013-020
exploit, third-party-advisory
-
exploit-db.com
/exploits/27044
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2013-7471
- NVD CVE-2013-7471
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.