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

> Remote attackers can execute arbitrary SQL commands via the session ID in the DB_eSession library, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v453-9c8g-w373

## What is CVE-2006-0774?

CVE-2006-0774 is a high-severity SQL injection vulnerability in n/a, published on 19 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in deleteSession() in DB_eSession library 1.0.2 and earlier, as used in multiple products, allows remote attackers to execute arbitrary SQL commands via the $_sess_id_set variable, which is usually derived from PHPSESSID.

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

It affects 1 product.


Products: Lawrence Osiris Db Esession.

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

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

## Is CVE-2006-0774 being exploited?

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

Public exploit code:

- Lawrence Osiris DB_eSession 1.0.2 - Class SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0774 is a high-severity SQL injection vulnerability in n/a, published on 19 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0774 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-0774/ (Markdown: https://insights.sbomify.com/CVE-2006-0774/index.md)
```

## Sources

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

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