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

> Remote attackers can execute arbitrary SQL commands via multiple parameters in the All In One Control Panel web application.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wpcp-vg3v-r8qr

## What is CVE-2006-5829?

CVE-2006-5829 is a medium-severity SQL injection vulnerability in n/a, published on 10 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in All In One Control Panel (AIOCP) 1.3.007 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) choosed_language parameter to (a) cp_dpage.php, (b) cp_news.php, (c) cp_forum_view.php, (d) cp_edit_user.php, (e) cp_newsletter.php, (f) cp_links.php, (g) cp_contact_us.php, (h) cp_login.php, and (i) cp_codice_fiscale.php in public/code/; (2) news_category parameter to public/code/cp_news.php; (3) nlmsg_nlcatid parameter to public/code/cp_newsletter.php; (4) links_category parameter to public/code/cp_links.php; (5) product_category_id parameter to public/code/cp_show_ec_products.php; (6) order_field parameter to public/code/cp_show_ec_products.php; (7) firstrow parameter to public/code/cp_users_online.php; and (8) orderdir parameter to public/code/cp_links_search.php.

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

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

It affects 1 product.


Products: Aiocp Aiocp.

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

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

## Is CVE-2006-5829 being exploited?

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

Public exploit code:

- AIOCP 1.3.x - 'cp_dpage.php' SQL Injection (exploitdb)
- AIOCP 1.3.x - 'cp_news.php' SQL Injection (exploitdb)
- AIOCP 1.3.x - 'cp_forum_view.php' SQL Injection (exploitdb)
- AIOCP 1.3.x - 'cp_edit_user.php' SQL Injection (exploitdb)
- AIOCP 1.3.x - 'cp_newsletter.php' SQL Injection (exploitdb)
- AIOCP 1.3.x - 'cp_links.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4782](https://insights.sbomify.com/CVE-2008-4782/): SQL injection in n/a (high 7.5)
- [CVE-2006-5831](https://insights.sbomify.com/CVE-2006-5831/): Code injection in n/a (high 7.5)
- [CVE-2007-2624](https://insights.sbomify.com/CVE-2007-2624/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2007-2625](https://insights.sbomify.com/CVE-2007-2625/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-5830](https://insights.sbomify.com/CVE-2006-5830/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5829 is a medium-severity SQL injection vulnerability in n/a, published on 10 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5829 exists.

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

## Sources

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

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