# CVE-2006-2067: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the userid parameter in MKPortal, potentially compromising forum data.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5q86-fgf8-6xg8

## What is CVE-2006-2067?

CVE-2006-2067 is a high-severity SQL injection vulnerability in n/a, published on 27 Apr 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in vb_board_functions.php in MKPortal 1.1, as used with vBulletin 3.5.4 and earlier, allows remote attackers to execute arbitrary SQL commands via the userid parameter.

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

It affects 1 product.


Products: Mkportal Mkportal.

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

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

## Is CVE-2006-2067 being exploited?

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

Public exploit code:

- MKPortal 1.1 - Multiple Input Validation Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0194](https://insights.sbomify.com/CVE-2007-0194/): Information disclosure in n/a (high 7.8)
- [CVE-2007-6467](https://insights.sbomify.com/CVE-2007-6467/): SQL injection in n/a (high 7.5)
- [CVE-2007-3814](https://insights.sbomify.com/CVE-2007-3814/): SQL injection in n/a (high 7.5)
- [CVE-2007-3637](https://insights.sbomify.com/CVE-2007-3637/): SQL injection in n/a (high 7.5)
- [CVE-2007-0192](https://insights.sbomify.com/CVE-2007-0192/): Cross-site request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2067 is a high-severity SQL injection vulnerability in n/a, published on 27 Apr 2006. It can be exploited 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-2006-2067 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-2067/ (Markdown: https://insights.sbomify.com/CVE-2006-2067/index.md)
```

## Sources

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

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