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

> Unspecified vulnerabilities in Seditio CMS, potentially SQL injection, allow attackers to read or modify data via affected admin and user modules.

- **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:** 7 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c2v6-5m74-mfqp

## What is CVE-2006-6344?

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

### Official description

Multiple unspecified vulnerabilities in Neocrome Seditio 1.10 and earlier have unknown impact and attack vectors related to (1) plugins/ipsearch/ipsearch.admin.php, and (2) pfs/pfs.edit.inc.php, (3) users/users.register.inc.php in system/core.  NOTE: the users.profile.inc.php vector is identified by CVE-2006-6177.  NOTE: these issues might be related to SQL injection.

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

It affects 1 product.


Products: Neocrome Seditio.

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

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

## Is CVE-2006-6344 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1411](https://insights.sbomify.com/CVE-2009-1411/): SQL injection in n/a (high 7.5)
- [CVE-2006-6177](https://insights.sbomify.com/CVE-2006-6177/): SQL injection in n/a (high 7.5)
- [CVE-2007-6202](https://insights.sbomify.com/CVE-2007-6202/): SQL injection in n/a (medium 6.8)
- [CVE-2006-6343](https://insights.sbomify.com/CVE-2006-6343/): SQL injection in n/a (medium 6.8)
- [CVE-2007-4057](https://insights.sbomify.com/CVE-2007-4057/): File upload in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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