# CVE-2006-7010: SQL injection in n/a

> A SQL injection vulnerability in Joomla allows attackers to potentially read or modify database contents due to improper variable type handling.

- **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 stated
- **Fix available:** No
- **Published:** 12 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-658h-q8jw-6rcq

## What is CVE-2006-7010?

CVE-2006-7010 is a high-severity SQL injection vulnerability in Joomla Joomla, published on 12 Feb 2007. It can be exploited over the network.

### Official description

The mosgetparam implementation in Joomla! before 1.0.10, does not set a variable's data type to integer when the variable's default value is numeric, which has unspecified impact and attack vectors, which may permit SQL injection attacks.

## Which versions are affected by CVE-2006-7010?

It affects 1 product.


Products: Joomla Joomla.

## How do I fix CVE-2006-7010?

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

## Is CVE-2006-7010 being exploited?

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

## Other vulnerabilities in Joomla Joomla

- [CVE-2008-3225](https://insights.sbomify.com/CVE-2008-3225/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-1047](https://insights.sbomify.com/CVE-2006-1047/): Other in n/a (critical 10.0)
- [CVE-2006-0303](https://insights.sbomify.com/CVE-2006-0303/): Other in n/a (critical 10.0)
- [CVE-2005-3773](https://insights.sbomify.com/CVE-2005-3773/): Unspecified vulnerability in Joomla! (critical 10.0)
- [CVE-2006-1028](https://insights.sbomify.com/CVE-2006-1028/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7010 and fix it if it is affected.

What it is: CVE-2006-7010 is a high-severity SQL injection vulnerability in Joomla Joomla, published on 12 Feb 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-7010 in the wild and no public exploit code.

Affected product: Joomla Joomla. 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-2006-7010/ (Markdown: https://insights.sbomify.com/CVE-2006-7010/index.md)
```

## Sources

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

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