CVE-2011-4559 json
SQL injection vulnerability in the Calendar module in vTiger CRM 5.2.1 and earlier allows remote attackers to execute arbitrary SQL command…
published 2011-11-28 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4485
- 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 the Calendar module in vTiger CRM 5.2.1 and earlier allows remote attackers to execute arbitrary SQL commands via the onlyforuser parameter in an index action to index.php.
Timeline
- First public exploit (EDB-36208)
- 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-36208 vTiger CRM 5.2 - 'onlyforuser' SQL Injection webapps, 2011-10-15
- seclists.org http://seclists.org/fulldisclosure/2011/Oct/224 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/49948 referenced PoC, tagged "exploit" by a source, unverified
- yehg.net http://yehg.net/lab/pr0js/advisories/%5BvTiger_5.2.1%5D_blind_sqlin 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
-
seclists.org
/fulldisclosure/2011/Oct/224
mailing-list, exploit
-
securityfocus.com
/bid/49948
vdb-entry, exploit
-
yehg.net
/lab/pr0js/advisories/%5BvTiger_5.2.1%5D_blind_sqlin
exploit
-
securityfocus.com
/archive/1/520006/100/0/threaded
mailing-list
-
osvdb.org
/76138
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/70344
vdb-entry
Sources
- CVE List CVE-2011-4559
- NVD CVE-2011-4559
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.