# CVE-2005-1833: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via multiple parameters in MyBB, potentially reading or modifying database contents.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4cjg-3gjp-8x4v

## What is CVE-2005-1833?

CVE-2005-1833 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 2 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in MyBulletinBoard (MyBB) 1.00 RC4 allow remote attackers to execute arbitrary SQL commands via the (1) eid parameter to calendar.php, (2) idsql parameter to online.php, (3) usersearch parameter to memberlist.php, (4) pid parameter to editpost.php, (5) fid parameter to forumdisplay.php, (6) tid parameter to newreply.php, (7) sid parameter to search.php, (8) tid or (9) pid parameter to showthread.php, (10) tid parameter to usercp2.php, (11) tid parameter to printthread.php, or (12) pid parameter to reputation.php.

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

It affects 1 product.


Products: Mybulletinboard Mybulletinboard.

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

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

## Is CVE-2005-1833 being exploited?

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

Public exploit code:

- MyBulletinBoard (MyBB) 1.00 RC4 - 'calendar.php' SQL Injection (exploitdb)

## 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-2005-1833 and fix it if it is affected.

What it is: CVE-2005-1833 is a high-severity SQL injection vulnerability in Mybulletinboard Mybulletinboard, published on 2 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1833 exists.

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-1833/ (Markdown: https://insights.sbomify.com/CVE-2005-1833/index.md)
```

## Sources

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

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