# CVE-2009-3480: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the p3 parameter in the iCRM Basic Joomla component.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m69v-4j9p-4g78

## What is CVE-2009-3480?

CVE-2009-3480 is a high-severity SQL injection vulnerability in n/a, published on 30 Sep 2009. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the iCRM Basic (com_icrmbasic) component 1.4.2.31 for Joomla! allows remote attackers to execute arbitrary SQL commands via the p3 parameter to index.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

## Which versions are affected by CVE-2009-3480?

It affects 1 product.


Products: Isygen Icrm Basic.

## How do I fix CVE-2009-3480?

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

## Is CVE-2009-3480 being exploited?

There is no known exploitation of CVE-2009-3480 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3480 and fix it if it is affected.

What it is: CVE-2009-3480 is a high-severity SQL injection vulnerability in n/a, published on 30 Sep 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3480 in the wild and no public exploit code.

Affected product: n/a. 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-2009-3480/ (Markdown: https://insights.sbomify.com/CVE-2009-3480/index.md)
```

## Sources

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

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