# CVE-2008-6326: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the email parameter in the login page of Simple Customer.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xq59-xf8q-8qpm

## What is CVE-2008-6326?

CVE-2008-6326 is a high-severity SQL injection vulnerability in n/a, published on 27 Feb 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in login.php in Simple Customer as downloaded on 20081118 allows remote attackers to execute arbitrary SQL commands via the email parameter.  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-2008-6326?

It affects 1 product.


Products: Simplecustomer Simple Customer.

## How do I fix CVE-2008-6326?

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

## Is CVE-2008-6326 being exploited?

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

Public exploit code:

- Simple Customer 1.2 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6332](https://insights.sbomify.com/CVE-2008-6332/): SQL injection in n/a (high 7.5)
- [CVE-2008-6081](https://insights.sbomify.com/CVE-2008-6081/): SQL injection in n/a (high 7.5)
- [CVE-2009-1637](https://insights.sbomify.com/CVE-2009-1637/): Missing authorization in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6326 and fix it if it is affected.

What it is: CVE-2008-6326 is a high-severity SQL injection vulnerability in n/a, published on 27 Feb 2009. 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-2008-6326 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-2008-6326/ (Markdown: https://insights.sbomify.com/CVE-2008-6326/index.md)
```

## Sources

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

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