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

> Remote attackers can modify SQL queries via the category parameter in adsearch.php, potentially reading 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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7545-65cx-3rpp

## What is CVE-2005-2253?

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

### Official description

SQL injection vulnerability in PhpAuction 2.5 allow remote attackers to modify SQL queries via the category parameter to adsearch.php. NOTE: there is evidence that viewnews.php may not be part of the PhpAuction product, so it is not included in this description.

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

It affects 1 product.


Products: Gianluca Baldo Phpauction.

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

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

## Is CVE-2005-2253 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3984](https://insights.sbomify.com/CVE-2006-3984/): Code injection in n/a (high 7.5)
- [CVE-2005-2252](https://insights.sbomify.com/CVE-2005-2252/): Auth bypass in n/a (high 7.5)
- [CVE-2002-0995](https://insights.sbomify.com/CVE-2002-0995/): Missing authorization in n/a (high 7.5)
- [CVE-2005-2255](https://insights.sbomify.com/CVE-2005-2255/): Path traversal in n/a (medium 6.4)
- [CVE-2005-2254](https://insights.sbomify.com/CVE-2005-2254/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2253 is a high-severity SQL injection vulnerability in n/a, published on 13 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2253 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-2253/ (Markdown: https://insights.sbomify.com/CVE-2005-2253/index.md)
```

## Sources

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

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