# CVE-2006-3829: Cross-site request forgery in n/a

> Remote attackers can trick administrators into deleting user accounts via CSRF, leading to unauthorized privilege escalation and data modification.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wpxj-m9rg-gvw6

## What is CVE-2006-3829?

CVE-2006-3829 is a medium-severity vulnerability in n/a, published on 25 Jul 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in bmc/admin.php in Kailash Nadh boastMachine (formerly bMachine) 3.1 and earlier allows remote attackers to perform unauthorized actions as an administrator and delete arbitrary user accounts via a delete_user action.

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

It affects 1 product.


Products: Kailash Nadh Boastmachine.

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

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

## Is CVE-2006-3829 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3827](https://insights.sbomify.com/CVE-2006-3827/): SQL injection in n/a (medium 6.5)
- [CVE-2006-3828](https://insights.sbomify.com/CVE-2006-3828/): SQL injection in n/a (medium 6.5)
- [CVE-2006-3831](https://insights.sbomify.com/CVE-2006-3831/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-3826](https://insights.sbomify.com/CVE-2006-3826/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-3830](https://insights.sbomify.com/CVE-2006-3830/): File upload in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3829 is a medium-severity vulnerability in n/a, published on 25 Jul 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-3829 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-3829/ (Markdown: https://insights.sbomify.com/CVE-2006-3829/index.md)
```

## Sources

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

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