# CVE-2005-3777: Missing authorization in n/a

> Remote attackers can delete or move private messages by modifying inbox form fields, requiring only a low-privilege user account.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rgjc-4jw4-4wgm

## What is CVE-2005-3777?

CVE-2005-3777 is a medium-severity missing authorization vulnerability in Mybulletinboard Mybulletinboard, published on 23 Nov 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MyBulletinBoard (MyBB) 1.0 PR2 Rev 686 allows remote attackers to delete or move private messages (PM) via modified fields in the inbox form.

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

It affects 1 product.


Products: Mybulletinboard Mybulletinboard.

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

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

## Is CVE-2005-3777 being exploited?

There is no known exploitation of CVE-2005-3777 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-2005-3777 and fix it if it is affected.

What it is: CVE-2005-3777 is a medium-severity missing authorization vulnerability in Mybulletinboard Mybulletinboard, published on 23 Nov 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3777 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-3777/ (Markdown: https://insights.sbomify.com/CVE-2005-3777/index.md)
```

## Sources

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

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