# CVE-2009-4206: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the id parameter in the admin link modification script, 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w76f-6568-v3qv

## What is CVE-2009-4206?

CVE-2009-4206 is a high-severity SQL injection vulnerability in n/a, published on 4 Dec 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in admin.link.modify.php in Million Dollar Text Links 1.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2009-4206?

It affects 1 product.


Products: Cmsnx Million Dollar Text Links.

## How do I fix CVE-2009-4206?

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

## Is CVE-2009-4206 being exploited?

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

Public exploit code:

- Million Dollar Text Links 1.0 - 'id' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1854](https://insights.sbomify.com/CVE-2009-1854/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4206 and fix it if it is affected.

What it is: CVE-2009-4206 is a high-severity SQL injection vulnerability in n/a, published on 4 Dec 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4206 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-2009-4206/ (Markdown: https://insights.sbomify.com/CVE-2009-4206/index.md)
```

## Sources

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

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