CVE-2013-3050 json
SQL injection vulnerability in ZAPms 1.41 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter to pr…
published 13y ago modified 4mo ago also EUVD-2013-2989
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in ZAPms 1.41 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter to product.
Is CVE-2013-3050 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-24942)
- Published
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-24942 ZAPms 1.41 - SQL Injection webapps, 2013-04-09
- securityfocus.com http://www.securityfocus.com/bid/58960 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/121202/ZAPms-1.41-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
exploit-db.com
/exploits/24942
exploit
-
securityfocus.com
/bid/58960
vdb-entry, exploit
-
packetstormsecurity.com
/files/121202/ZAPms-1.41-SQL-Injection.html
exploit
-
secunia.com
/advisories/52946
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/83313
vdb-entry
-
osvdb.org
/92236
vdb-entry
- zapms.de /open_source_cms_en
Sources
- CVE List CVE-2013-3050
- NVD CVE-2013-3050
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.