# CVE-2006-5221: Multiple SQL injection vulnerabilities in Cahier de texte 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) matiere_I


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cg54-j8wf-hwh3

## What is CVE-2006-5221?

CVE-2006-5221 is a high-severity vulnerability in n/a, published on 10 Oct 2006. 

### Official description

Multiple SQL injection vulnerabilities in Cahier de texte 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) matiere_ID parameter in lire.php or the (2) classe_ID parameter in lire_a_faire.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Cahier De Textes Cahier De Textes.

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

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

## Is CVE-2006-5221 being exploited?

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

Public exploit code:

- Cahier de texte 2.0 - 'lire.php' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6849](https://insights.sbomify.com/CVE-2006-6849/): Auth bypass in n/a (high 7.5)
- [CVE-2006-6253](https://insights.sbomify.com/CVE-2006-6253/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-6254](https://insights.sbomify.com/CVE-2006-6254/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5221 is a high-severity vulnerability in n/a, published on 10 Oct 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5221 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-2006-5221/ (Markdown: https://insights.sbomify.com/CVE-2006-5221/index.md)
```

## Sources

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

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