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

> Remote attackers can execute arbitrary SQL commands via the pid parameter in Web4Future Affiliate Manager PRO, 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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9p38-r99r-g3mg

## What is CVE-2005-4037?

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

### Official description

SQL injection vulnerability in functions.php in Web4Future Affiliate Manager PRO 4.1 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter.

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


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

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

## Is CVE-2005-4037 being exploited?

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

Public exploit code:

- Web4Future Affiliate Manager PRO 4.1 - 'functions.php' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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