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

> Remote attackers can execute arbitrary SQL commands and code via the sess_username cookie in PHP121, leading to full system compromise.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 19 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mhhr-394j-8m96

## What is CVE-2006-1828?

CVE-2006-1828 is a medium-severity SQL injection vulnerability in n/a, published on 19 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 php121language.php in PHP121 1.4 allows remote attackers to execute arbitrary SQL commands and execute arbitrary code via the sess_username variable, as set by the php121un HTTP COOKIE parameter, which is used in multiple files including php121login.php.  NOTE: the code execution occurs because the SQL query results are used in an include statement.

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

It affects 1 product.


Products: Php121 Php121 Instant Messenger.

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

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

## Is CVE-2006-1828 being exploited?

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

Public exploit code:

- PHP121 Instant Messenger 1.4 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1908](https://insights.sbomify.com/CVE-2007-1908/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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