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

> Remote attackers can execute arbitrary SQL commands in Blue Smiley Organizer, 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 stated
- **Fix available:** No
- **Published:** 12 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-726v-gcr4-pcgr

## What is CVE-2006-5237?

CVE-2006-5237 is a high-severity SQL injection vulnerability in n/a, published on 12 Oct 2006. It can be exploited over the network.

### Official description

SQL injection vulnerability in Blue Smiley Organizer before 4.46 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

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

It affects 1 product.


Products: Blue Smiley Organizer Blue Smiley Organizer.

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

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

## Is CVE-2006-5237 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5238](https://insights.sbomify.com/CVE-2006-5238/): Unspecified vulnerability in the file upload module in Blue Smiley Organizer before 4.45 has unknown impact and attack vectors. (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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