CVE-2013-2568 in the critical feed json
A Command Injection vulnerability exists in Zavio IP Cameras through 1.6.3 via the ap parameter to /cgi-bin/mft/wireless_mft.cgi, which cou…
published 6y ago modified 4mo ago also EUVD-2013-2510
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 48.5%
- EPSS 48.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
A Command Injection vulnerability exists in Zavio IP Cameras through 1.6.3 via the ap parameter to /cgi-bin/mft/wireless_mft.cgi, which could let a remote malicious user execute arbitrary code.
Is CVE-2013-2568 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 FencerTimeline
- First public exploit (EDB-25815)
- Published
Exploit prediction
48.54% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-25815 Zavio IP Cameras Firmware 1.6.03 - Multiple Vulnerabilities webapps, 2013-05-29
- coresecurity.com https://www.coresecurity.com/advisories/zavio-ip-cameras-multiple-vulnerabilities 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 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
coresecurity.com
/advisories/zavio-ip-cameras-multiple-vulnerabilities
exploit, third-party-advisory
-
securityfocus.com
/bid/60190
third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/84569
third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/cve/CVE-2013-2568/page1/
third-party-advisory, vdb-entry
-
vulmon.com
/vulnerabilitydetails?qid=CVE-2013-2568
third-party-advisory
Sources
- CVE List CVE-2013-2568
- NVD CVE-2013-2568
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.