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

> Remote attackers can execute arbitrary SQL commands via multiple parameters in TGS Content Management, 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:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xqh8-x69c-4q93

## What is CVE-2009-2929?

CVE-2009-2929 is a high-severity SQL injection vulnerability in n/a, published on 21 Aug 2009. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in TGS Content Management 0.x allow remote attackers to execute arbitrary SQL commands via the (1) tgs_language_id, (2) tpl_dir, (3) referer, (4) user-agent, (5) site, (6) option, (7) db_optimization, (8) owner, (9) admin_email, (10) default_language, and (11) db_host parameters to cms/index.php; and the (12) cmd, (13) s_dir, (14) minutes, (15) s_mask, (16) test3_mp, (17) test15_file1, (18) submit, (19) brute_method, (20) ftp_server_port, (21) userfile14, (22) subj, (23) mysql_l, (24) action, and (25) userfile1 parameters to cms/frontpage_ception.php. NOTE: some of these parameters may be applicable only in nonstandard versions of the product, and cms/frontpage_ception.php may be cms/frontpage_caption.php in all released versions.

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

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

It affects 1 product.


Products: Tgs-Cms Tgs Content Management.

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

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

## Is CVE-2009-2929 being exploited?

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

Public exploit code:

- tgs CMS 0.x - Cross-Site Scripting / SQL Injection / File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2928](https://insights.sbomify.com/CVE-2009-2928/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-6839](https://insights.sbomify.com/CVE-2008-6839/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2929 is a high-severity SQL injection vulnerability in n/a, published on 21 Aug 2009. It can be exploited 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-2009-2929 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-2929/ (Markdown: https://insights.sbomify.com/CVE-2009-2929/index.md)
```

## Sources

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

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