# CVE-2005-3369: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands and potentially upload files via vulnerable parameters in the Info-DB module.

- **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:** 29 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-63g2-5r57-6pg5

## What is CVE-2005-3369?

CVE-2005-3369 is a high-severity SQL injection vulnerability in n/a, published on 29 Oct 2005. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the Info-DB module (info_db.php) in Woltlab Burning Board 2.7 and earlier allow remote attackers to execute arbitrary SQL commands and possibly upload files via the (1) fileid and (2) subkatid parameters.

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


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

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

## Is CVE-2005-3369 being exploited?

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

Public exploit code:

- Woltlab 1.1/2.x - 'Info-DB Info_db.php' Multiple SQL Injections (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3369 is a high-severity SQL injection vulnerability in n/a, published on 29 Oct 2005. 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-2005-3369 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-2005-3369/ (Markdown: https://insights.sbomify.com/CVE-2005-3369/index.md)
```

## Sources

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

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