# CVE-2005-4200: Other in n/a

> Multiple unspecified vulnerabilities in MyBB allow attackers to potentially compromise the forum, requiring an upgrade to a secure version.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qqw5-x59w-fv9f

## What is CVE-2005-4200?

CVE-2005-4200 is a critical vulnerability in Mybulletinboard Mybulletinboard, published on 13 Dec 2005. It can be exploited over the network.

### Official description

Multiple unspecified vulnerabilities in MyBulletinBoard (MyBB) before 1.0 have unknown impact and attack vectors, a different set of vulnerabilities than those identified by CVE-2005-4199.

## Which versions are affected by CVE-2005-4200?

It affects 1 product.


Products: Mybulletinboard Mybulletinboard.

## How do I fix CVE-2005-4200?

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

## Is CVE-2005-4200 being exploited?

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

## Other vulnerabilities in Mybulletinboard Mybulletinboard

- [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)
- [CVE-2006-3760](https://insights.sbomify.com/CVE-2006-3760/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4200 and fix it if it is affected.

What it is: CVE-2005-4200 is a critical vulnerability in Mybulletinboard Mybulletinboard, published on 13 Dec 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2005-4200 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-2005-4200/ (Markdown: https://insights.sbomify.com/CVE-2005-4200/index.md)
```

## Sources

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

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