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

> Remote attackers can execute arbitrary SQL commands via mail.php parameters, potentially compromising data integrity and confidentiality.

- **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:** 16 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qx5c-fgc6-66q9

## What is CVE-2006-5926?

CVE-2006-5926 is a high-severity SQL injection vulnerability in n/a, published on 16 Nov 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in mail.php in Vallheru before 1.0.7 allow remote attackers to execute arbitrary SQL commands via the (1) id or (2) to parameters.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Vallheru Vallheru.

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

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

## Is CVE-2006-5926 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1408](https://insights.sbomify.com/CVE-2007-1408/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5926 is a high-severity SQL injection vulnerability in n/a, published on 16 Nov 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5926 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-2006-5926/ (Markdown: https://insights.sbomify.com/CVE-2006-5926/index.md)
```

## Sources

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

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