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

> Remote attackers can execute arbitrary SQL commands in the Mambo Resident component if magic_quotes_gpc is disabled, compromising database integrity.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 4 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5mgw-j9fq-4fr9

## What is CVE-2009-4199?

CVE-2009-4199 is a medium-severity SQL injection vulnerability in n/a, published on 4 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the Mambo Resident (aka Mos Res or com_mosres) component 1.0f for Mambo and Joomla!, when magic_quotes_gpc is disabled, allow remote attackers to execute arbitrary SQL commands via the (1) property_uid parameter in a viewproperty action to index.php and the (2) regID parameter in a showregion action to index.php.

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

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

It affects 1 product.


Products: Mamboforge Com Mosres.

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

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

## Is CVE-2009-4199 being exploited?

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

Public exploit code:

- Joomla! Component com_mosres - Multiple SQL Injections (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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