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

> Remote attackers can inject arbitrary SQL commands via the gameid parameter in the favorites module, potentially compromising database integrity.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8r5x-26x3-9q3c

## What is CVE-2005-4702?

CVE-2005-4702 is a medium-severity SQL injection vulnerability in n/a, published on 1 Feb 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the favorites module in index.php in IPBProArcade 2.5.2 allows remote attackers to inject arbitrary SQL commands via the gameid parameter.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. In addition, the demonstration code as used by third parties suggests that this might be a different type of vulnerability related to shell metacharacters.  Finally, this could be a rediscovery of CVE-2004-1430.

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

It affects 1 product.


Products: Ipbproarcade Ipbproarcade.

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

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

## Is CVE-2005-4702 being exploited?

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

Public exploit code:

- IPBProArcade 2.5.2 - 'GameID' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1536](https://insights.sbomify.com/CVE-2004-1536/): SQL injection in n/a (high 7.5)
- [CVE-2004-1430](https://insights.sbomify.com/CVE-2004-1430/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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