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

> Remote attackers can read private forum posts by modifying the mid parameter when Tree View is enabled in FUDForum.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** Yes
- **Published:** 17 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j74p-362c-vrf2

## What is CVE-2005-2600?

CVE-2005-2600 is a medium-severity missing authorization vulnerability in n/a, published on 17 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FUDForum 2.6.15 with "Tree View" enabled, as used in other products such as phpgroupware and egroupware, allows remote attackers to read private posts via a modified mid parameter.

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

It affects 1 product.


Products: Ilia Alshanetsky Fudforum.

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

Upgrade to a fixed version.

## Is CVE-2005-2600 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2781](https://insights.sbomify.com/CVE-2005-2781/): File upload in n/a (high 7.5)
- [CVE-2002-1421](https://insights.sbomify.com/CVE-2002-1421/): SQL injection vulnerabilities in FUDforum before 2.2.0 allow remote attackers to perform unauthorized database operations via (1) report.php (high 7.5)
- [CVE-2002-1422](https://insights.sbomify.com/CVE-2002-1422/): Path traversal in n/a (medium 5.0)
- [CVE-2002-1423](https://insights.sbomify.com/CVE-2002-1423/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2600 is a medium-severity missing authorization vulnerability in n/a, published on 17 Aug 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-2600 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-2005-2600/ (Markdown: https://insights.sbomify.com/CVE-2005-2600/index.md)
```

## Sources

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

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