# CVE-2008-6049: SQL injection vulnerability in index.php in TinyMCE 2.0.1 allows remote attackers to execute arbitrary SQL commands via the menuID parameter.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Feb 2009
- **Updated:** 23 Oct 2017

## What is CVE-2008-6049?

CVE-2008-6049 is a vulnerability, published on 4 Feb 2009. 

### Official description

SQL injection vulnerability in index.php in TinyMCE 2.0.1 allows remote attackers to execute arbitrary SQL commands via the menuID parameter.  NOTE: CVE and multiple reliable third parties dispute this issue, since TinyMCE does not contain index.php or any PHP code.  This may be an issue in a product that has integrated TinyMCE

## Which versions are affected by CVE-2008-6049?


## How do I fix CVE-2008-6049?

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

## Is CVE-2008-6049 being exploited?

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

Public exploit code:

- TinyMCE 2.0.1 - 'menuID' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6049 and fix it if it is affected.

What it is: CVE-2008-6049 is a vulnerability, published on 4 Feb 2009. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6049 exists.

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-2008-6049/ (Markdown: https://insights.sbomify.com/CVE-2008-6049/index.md)
```

## Sources

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

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