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

> Remote authenticated administrators can execute arbitrary SQL commands in PunBB, potentially compromising the database.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2006
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-ccxg-86pq-6mj7

## What is CVE-2006-5738?

CVE-2006-5738 is a high-severity SQL injection vulnerability in n/a, published on 6 Nov 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in PunBB before 1.2.14 allow remote authenticated administrators to execute arbitrary SQL commands via unspecified vectors.

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

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

It affects 1 product.


Products: Punbb Punbb.

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

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

## Is CVE-2006-5738 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3335](https://insights.sbomify.com/CVE-2008-3335/): Command injection in n/a (critical 10.0)
- [CVE-2006-1090](https://insights.sbomify.com/CVE-2006-1090/): Denial of service in n/a (high 7.8)
- [CVE-2007-2234](https://insights.sbomify.com/CVE-2007-2234/): SQL injection in n/a (high 7.5)
- [CVE-2006-5735](https://insights.sbomify.com/CVE-2006-5735/): Path traversal in n/a (high 7.5)
- [CVE-2005-3518](https://insights.sbomify.com/CVE-2005-3518/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5738 is a high-severity SQL injection vulnerability in n/a, published on 6 Nov 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-5738 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-5738/ (Markdown: https://insights.sbomify.com/CVE-2006-5738/index.md)
```

## Sources

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

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