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

> Remote attackers can execute arbitrary SQL commands in MyBB, potentially compromising database 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 needed
- **Fix available:** No
- **Published:** 21 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-45fr-mwhc-fjp4

## What is CVE-2006-3760?

CVE-2006-3760 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 21 Jul 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in MyBB (aka MyBulletinBoard) 1.1.4 allow remote attackers to execute arbitrary SQL commands via unspecified vectors.

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

It affects 1 product.


Products: Mybulletinboard Mybulletinboard.

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

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

## Is CVE-2006-3760 being exploited?

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

## Other vulnerabilities in Mybulletinboard Mybulletinboard

- [CVE-2005-4200](https://insights.sbomify.com/CVE-2005-4200/): Other in n/a (critical 10.0)
- [CVE-2009-2230](https://insights.sbomify.com/CVE-2009-2230/): SQL injection in n/a (high 7.5)
- [CVE-2008-0382](https://insights.sbomify.com/CVE-2008-0382/): Code injection in n/a (high 7.5)
- [CVE-2007-2211](https://insights.sbomify.com/CVE-2007-2211/): SQL injection in n/a (high 7.5)
- [CVE-2006-3758](https://insights.sbomify.com/CVE-2006-3758/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3760 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 21 Jul 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3760 in the wild and no public exploit code.

Affected product: Mybulletinboard Mybulletinboard. 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-3760/ (Markdown: https://insights.sbomify.com/CVE-2006-3760/index.md)
```

## Sources

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

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