# CVE-2006-2065: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands and potentially PHP code via the surveyid cookie in PHPSurveyor.

- **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:** 27 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m79g-h2ww-gqhg

## What is CVE-2006-2065?

CVE-2006-2065 is a high-severity SQL injection vulnerability in n/a, published on 27 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in save.php in PHPSurveyor 0.995 and earlier allows remote attackers to execute arbitrary SQL commands via the surveyid cookie.  NOTE: this issue could be leveraged to execute arbitrary PHP code, as demonstrated by inserting directory traversal sequences into the database, which are then processed by the thissurvey['language'] variable.

## Which versions are affected by CVE-2006-2065?

It affects 1 product.


Products: Phpsurveyor Phpsurveyor.

## How do I fix CVE-2006-2065?

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

## Is CVE-2006-2065 being exploited?

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

Public exploit code:

- PHPSurveyor 0.995 - 'surveyid' Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2065 and fix it if it is affected.

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

## Sources

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

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