# CVE-2011-4833: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in SugarCRM's Leads module via vulnerable parameters, potentially accessing or modifying data.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q889-r359-8p38

## What is CVE-2011-4833?

CVE-2011-4833 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 15 Dec 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2011-4833?

It affects 1 product.


Products: Sugarcrm Sugarcrm.

## How do I fix CVE-2011-4833?

No fix has been published for CVE-2011-4833 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-4833 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4833 exists.

Public exploit code:

- SugarCRM Community Edition 6.3.0RC1 - 'index.php' Multiple SQL Injections (exploitdb)

## Other vulnerabilities in Sugarcrm Sugarcrm

- [CVE-2023-22952](https://insights.sbomify.com/CVE-2023-22952/): Multiple SugarCRM Products Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2004-1225](https://insights.sbomify.com/CVE-2004-1225/): SQL injection in n/a (critical 10.0)
- [CVE-2020-7472](https://insights.sbomify.com/CVE-2020-7472/): Path traversal in n/a (critical 9.8)
- [CVE-2012-0694](https://insights.sbomify.com/CVE-2012-0694/): Deserialization in n/a (critical 9.8)
- [CVE-2014-3244](https://insights.sbomify.com/CVE-2014-3244/): XML external entity in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4833 and fix it if it is affected.

What it is: CVE-2011-4833 is a high-severity SQL injection vulnerability in Sugarcrm Sugarcrm, published on 15 Dec 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4833 exists.

Affected product: Sugarcrm Sugarcrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-4833/ (Markdown: https://insights.sbomify.com/CVE-2011-4833/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4833
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4833
- OSV: https://osv.dev/vulnerability/CVE-2011-4833

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-4833/
Summaries are generated and may contain mistakes; the official description above is the record.