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

> Remote attackers can execute arbitrary SQL commands via multiple parameters in Infopop UBB.Threads, potentially compromising database integrity and confidentiality.

- **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:** 28 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9q4j-627x-95w7

## What is CVE-2005-2058?

CVE-2005-2058 is a high-severity SQL injection vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Infopop UBB.Threads before 6.5.2 Beta allow remote attackers to execute arbitrary SQL commands via the Number parameter to (1) download.php, (2) modifypost.php, (3) mailthread.php, or (4) notifymod.php, (5) month or (6) year parameter to calendar.php, (7) message parameter to viewmessage.php, (8) main parameter to addfav.php, or (9) posted parameter to grabnext.php.

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

It affects 1 product.


Products: Ubbcentral Ubb.threads.

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

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

## Is CVE-2005-2058 being exploited?

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

Public exploit code:

- UBBCentral UBB.Threads 5.5.1/6.x - 'download.php?Number' SQL Injection (exploitdb)
- UBBCentral UBB.Threads 5.5.1/6.x - 'calendar.php' Multiple SQL Injections (exploitdb)
- UBBCentral UBB.Threads 5.5.1/6.x - 'modifypost.php?Number' SQL Injection (exploitdb)
- UBBCentral UBB.Threads 5.5.1/6.x - 'viewmessage.php?message' SQL Injection (exploitdb)
- UBBCentral UBB.Threads 5.5.1/6.x - 'addfav.php?main' SQL Injection (exploitdb)
- UBBCentral UBB.Threads 5.5.1/6.x - 'notifymod.php?Number' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6970](https://insights.sbomify.com/CVE-2008-6970/): SQL injection in n/a (high 7.5)
- [CVE-2007-1956](https://insights.sbomify.com/CVE-2007-1956/): SQL injection in n/a (high 7.5)
- [CVE-2006-5136](https://insights.sbomify.com/CVE-2006-5136/): Code injection in n/a (high 7.5)
- [CVE-2006-0545](https://insights.sbomify.com/CVE-2006-0545/): SQL injection in n/a (high 7.5)
- [CVE-2005-0726](https://insights.sbomify.com/CVE-2005-0726/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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