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

> Remote attackers can execute arbitrary SQL statements in PunBB via the user profile edit module, potentially accessing or modifying database contents.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cf42-v5r9-fg8j

## What is CVE-2005-2193?

CVE-2005-2193 is a high-severity SQL injection vulnerability in n/a, published on 10 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the user profile edit module in profile.php for PunBB 1.2.5 and earlier allows remote attackers to execute arbitrary SQL statements via the temp array, which is not initialized before it is used and prevents the attacker-supplied portions of the array from being properly escaped.

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

It affects 1 product.


Products: Punbb Punbb.

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

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

## Is CVE-2005-2193 being exploited?

There is no known exploitation of CVE-2005-2193 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-3335](https://insights.sbomify.com/CVE-2008-3335/): Command injection in n/a (critical 10.0)
- [CVE-2006-1090](https://insights.sbomify.com/CVE-2006-1090/): Denial of service in n/a (high 7.8)
- [CVE-2007-2234](https://insights.sbomify.com/CVE-2007-2234/): SQL injection in n/a (high 7.5)
- [CVE-2006-5735](https://insights.sbomify.com/CVE-2006-5735/): Path traversal in n/a (high 7.5)
- [CVE-2005-3518](https://insights.sbomify.com/CVE-2005-3518/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2193 is a high-severity SQL injection vulnerability in n/a, published on 10 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2193 in the wild and no public exploit code.

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-2193/ (Markdown: https://insights.sbomify.com/CVE-2005-2193/index.md)
```

## Sources

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

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