CVE-2012-1911 json
Multiple SQL injection vulnerabilities in PHP Address Book 6.2.12 and earlier allow remote attackers to execute arbitrary SQL commands via…
published 2012-09-09 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1920
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in PHP Address Book 6.2.12 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) to_group parameter to group.php or (2) id parameter to vcard.php. NOTE: the edit.php vector is already covered by CVE-2008-2565.
Timeline
- First public exploit (EDB-18578)
- Published
Exploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-18578 PHP Address Book 6.2.12 - Multiple Vulnerabilities webapps, 2012-03-10
- securityfocus.com http://www.securityfocus.com/bid/52396 referenced PoC, tagged "exploit" by a source, unverified
- darksecurity.de http://www.darksecurity.de/advisories/2012/SSCHADV2012-007.txt 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/18578
exploit
-
securityfocus.com
/bid/52396
vdb-entry, exploit
-
darksecurity.de
/advisories/2012/SSCHADV2012-007.txt
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/73943
vdb-entry
- sourceforge.net /tracker/?func=detail&aid=3501716&group_id=157964&atid=805929
- sourceforge.net /tracker/?func=detail&aid=3496653&group_id=157964&atid=805929
Sources
- CVE List CVE-2012-1911
- NVD CVE-2012-1911
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.