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

> Remote attackers can execute arbitrary SQL commands in e107 CMS, potentially compromising database integrity and confidentiality.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2006-2602, GHSA-j2cg-4gmg-75p3

## What is CVE-2006-2590?

CVE-2006-2590 is a medium-severity SQL injection vulnerability in E107 E107, published on 25 May 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in e107 before 0.7.5 allows remote attackers to execute arbitrary SQL commands via unknown attack vectors.

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

It affects 1 product.


Products: E107 E107.

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

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

## Is CVE-2006-2590 being exploited?

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

## Other vulnerabilities in E107 E107

- [CVE-2021-27885](https://insights.sbomify.com/CVE-2021-27885/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10753](https://insights.sbomify.com/CVE-2016-10753/): Deserialization in n/a (high 8.8)
- [CVE-2018-15901](https://insights.sbomify.com/CVE-2018-15901/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-50916](https://insights.sbomify.com/CVE-2022-50916/): e107 CMS v3.2.1 - Upload restriction bypass (Authenticated [Admin])+ Server file override (high 8.7)
- [CVE-2022-50907](https://insights.sbomify.com/CVE-2022-50907/): e107 CMS v3.2.1 - Admin Upload Restriction Bypass + RCE (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2590 is a medium-severity SQL injection vulnerability in E107 E107, published on 25 May 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2590 in the wild and no public exploit code.

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

## Sources

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

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