# CVE-2009-1742: SQL injection in n/a

> Remote attackers can execute SQL injection attacks via crafted keyword sequences in the id parameter, bypassing filters to access or modify database content.

- **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:** 20 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4hh7-83pv-xh8h

## What is CVE-2009-1742?

CVE-2009-1742 is a high-severity SQL injection vulnerability in n/a, published on 20 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

code.php in PC4Arb Pc4 Uploader 9.0 and earlier makes it easier for remote attackers to conduct SQL injection attacks via crafted keyword sequences that are removed from a filter in the id parameter in a banner action, as demonstrated via the "UNIunionON" string, which is collapsed into "UNION" by the filter_sql function.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2009-1742?

It affects 1 product.


Products: Pc4arb Pc4 Uploader.

## How do I fix CVE-2009-1742?

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

## Is CVE-2009-1742 being exploited?

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

Public exploit code:

- Pc4Uploader 9.0 - Blind SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2180](https://insights.sbomify.com/CVE-2009-2180/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1742 and fix it if it is affected.

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

## Sources

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

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