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

> Authenticated users can bypass forum permissions to reply in arbitrary forums and perform unauthorized actions due to flawed permission assembly.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 6 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-77rw-7fvw-mgvf

## What is CVE-2006-5729?

CVE-2006-5729 is a medium-severity missing authorization vulnerability in n/a, published on 6 Nov 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Yazd Discussion Forum before 3.0 beta does not properly manage forum permissions, which allows remote authenticated users to (1) reply to a message in an arbitrary forum, if authorized to create a message in any forum; and (2) perform certain unauthorized forum actions, related to an "error in how the permissions were assembled" that assigns extra permissions to users.

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

It affects 1 product.


Products: Yazd Yazd Discussion Forum.

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

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

## Is CVE-2006-5729 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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