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

> Remote attackers can execute arbitrary SQL commands via the clientid parameter in phpAdsNew and phpPgAds, potentially compromising database integrity.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rpqr-x3mc-8f22

## What is CVE-2005-2636?

CVE-2005-2636 is a high-severity SQL injection vulnerability in n/a, published on 20 Aug 2005. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in lib-view-direct.inc.php in phpAdsNew and phpPgAds before 2.0.6 allows remote attackers to execute arbitrary SQL commands via the clientid parameter.

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

It affects 2 products.


Products: Phpadsnew Phpadsnew, Phppgads Phppgads.

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

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

## Is CVE-2005-2636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0486](https://insights.sbomify.com/CVE-2007-0486/): Code injection in n/a (high 7.5)
- [CVE-2006-6415](https://insights.sbomify.com/CVE-2006-6415/): Code injection in n/a (high 7.5)
- [CVE-2005-3646](https://insights.sbomify.com/CVE-2005-3646/): SQL injection in n/a (high 7.5)
- [CVE-2001-1054](https://insights.sbomify.com/CVE-2001-1054/): File upload in n/a (high 7.5)
- [CVE-2006-5437](https://insights.sbomify.com/CVE-2006-5437/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2636 is a high-severity SQL injection vulnerability in n/a, published on 20 Aug 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2636 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-2636/ (Markdown: https://insights.sbomify.com/CVE-2005-2636/index.md)
```

## Sources

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

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