# CVE-2006-1111: Information disclosure in n/a

> Remote attackers can obtain sensitive usernames and passwords via a crafted msg parameter in Aztek Forum, leading to information disclosure.

- **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:** 9 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v53h-c4r9-mg75

## What is CVE-2006-1111?

CVE-2006-1111 is a high-severity vulnerability in n/a, published on 9 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Aztek Forum 4.0 allows remote attackers to obtain sensitive information via a "*/*" in the msg parameter to index.php, which reveals usernames and passwords in a MySQL error message, possibly due to a forced SQL error or SQL injection.

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

It affects 1 product.


Products: Aztek Forum Aztek Forum.

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

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

## Is CVE-2006-1111 being exploited?

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

Public exploit code:

- Aztek Forum 4.00 - Cross-Site Scripting / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0598](https://insights.sbomify.com/CVE-2007-0598/): SQL injection in n/a (high 7.5)
- [CVE-2007-0599](https://insights.sbomify.com/CVE-2007-0599/): Code injection in n/a (high 7.5)
- [CVE-2007-0601](https://insights.sbomify.com/CVE-2007-0601/): Security feature bypass in n/a (high 7.5)
- [CVE-2007-0596](https://insights.sbomify.com/CVE-2007-0596/): Code injection in n/a (medium 6.0)
- [CVE-2007-0597](https://insights.sbomify.com/CVE-2007-0597/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1111 is a high-severity vulnerability in n/a, published on 9 Mar 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-1111 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-1111/ (Markdown: https://insights.sbomify.com/CVE-2006-1111/index.md)
```

## Sources

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

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