# CVE-2006-5597: Missing authorization in n/a

> Remote attackers can add or modify arbitrary user accounts in MiniHTTP Web Forum by manipulating specific parameters without authentication.

- **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:** 28 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vcr-vjpj-p33c

## What is CVE-2006-5597?

CVE-2006-5597 is a high-severity missing authorization vulnerability in n/a, published on 28 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

join.asp in MiniHTTP Web Forum & File Server PowerPack 4.0 allows remote attackers to add or modify arbitrary user accounts via modified (1) frmMailBox and (2) frmUserPass parameters.

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

It affects 1 product.


Products: Minihttp Web Forum File Sharing Sever Powerpack.

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

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

## Is CVE-2006-5597 being exploited?

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

Public exploit code:

- MiniHTTPServer Web Forum & File Sharing Server 4.0 - Add User (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5597 is a high-severity missing authorization vulnerability in n/a, published on 28 Oct 2006. 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-2006-5597 exists.

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

## Sources

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

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