Skip to content
Fencer Intel
high 7.5

CVE-2011-4833 json

Multiple SQL injection vulnerabilities in the Leads module in SugarCRM 6.1 before 6.1.7, 6.2 before 6.2.4, 6.3 before 6.3.0RC3, and 6.4 bef…

published 2011-12-15 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4751

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
1
Exploit-DB

Summary

Multiple SQL injection vulnerabilities in the Leads module in SugarCRM 6.1 before 6.1.7, 6.2 before 6.2.4, 6.3 before 6.3.0RC3, and 6.4 before 6.4.0beta1 allow remote attackers to execute arbitrary SQL commands via the (1) where and (2) order parameters in a get_full_list action to index.php.

Timeline

  1. First public exploit (EDB-36384)
  2. Published

Exploit prediction

1.91% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-36384 SugarCRM Community Edition 6.3.0RC1 - 'index.php' Multiple SQL Injections webapps, 2011-11-30
  • sugarcrm.com http://www.sugarcrm.com/crm/support/bugs.html#issue_47839 referenced PoC, tagged "exploit" by a source, unverified
  • htbridge.ch https://www.htbridge.ch/advisory/sql_injection_in_sugarcrm.html referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/77459 referenced PoC, tagged "exploit" by a source, unverified
  • sugarcrm.com http://www.sugarcrm.com/crm/support/bugs.html#issue_47805 referenced PoC, tagged "exploit" by a source, unverified
  • securitytracker.com http://securitytracker.com/id?1026369 referenced PoC, tagged "exploit" by a source, unverified
  • sugarcrm.com http://www.sugarcrm.com/crm/support/bugs.html#issue_47806 referenced PoC, tagged "exploit" by a source, unverified
  • sugarcrm.com http://www.sugarcrm.com/crm/support/bugs.html#issue_47800 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

Sources

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.