# CVE-2003-1176: Missing authorization in n/a

> Remote attackers can read or write to private forums by modifying the forum ID parameter in quote mode, requiring low privileges.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x29h-34cg-7pq6

## What is CVE-2003-1176?

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

### Official description

post_message_form.asp in Web Wiz Forums 6.34 through 7.5, when quote mode is used, allows remote attackers to read or write to private forums by modifying the FID (forum ID) parameter.

## Which versions are affected by CVE-2003-1176?

It affects 1 product.


Products: Bdc Enterprises Web Wiz Forums.

## How do I fix CVE-2003-1176?

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

## Is CVE-2003-1176 being exploited?

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

Public exploit code:

- Web Wiz Forum 6.34/7.0/7.5 - Unauthorized Private Forum Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2228](https://insights.sbomify.com/CVE-2005-2228/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1176 and fix it if it is affected.

What it is: CVE-2003-1176 is a medium-severity missing authorization vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1176 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-2003-1176/ (Markdown: https://insights.sbomify.com/CVE-2003-1176/index.md)
```

## Sources

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

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