# CVE-2009-4140: File upload in n/a

> Authenticated attackers can upload malicious files to execute arbitrary code when register_globals is enabled in Open Flash Chart.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x396-wp63-mv42

## What is CVE-2009-4140?

CVE-2009-4140 is a high-severity vulnerability in n/a, published on 22 Dec 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in ofc_upload_image.php in Open Flash Chart v2 Beta 1 through v2 Lug Wyrm Charmer, as used in Piwik 0.2.35 through 0.4.3, Woopra Analytics Plugin before 1.4.3.2, and possibly other products, when register_globals is enabled, allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension through the name parameter with the code in the HTTP_RAW_POST_DATA parameter, then accessing it via a direct request to the file in tmp-upload-images/.

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

It affects 2 products.


Products: Matomo Matomo, Teethgrinder.co.uk Open Flash Chart.

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

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

## Is CVE-2009-4140 being exploited?

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

Public exploit code:

- Open Flash Chart v2 Arbitrary File Upload (metasploit)
- Piwik Open Flash Chart - Remote Code Execution (exploitdb)
- OpenEMR 4.1.1 - 'ofc_upload_image.php' Arbitrary File Upload (exploitdb)
- OpenEMR PHP File Upload Vulnerability (metasploit)
- OpenEMR - Arbitrary '.PHP' File Upload (Metasploit) (exploitdb)
- Joomla! Component com_civicrm 4.2.2 - Remote Code Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-7815](https://insights.sbomify.com/CVE-2015-7815/): Path traversal in n/a (high 7.5)
- [CVE-2015-7816](https://insights.sbomify.com/CVE-2015-7816/): Deserialization in n/a (high 7.5)
- [CVE-2009-4137](https://insights.sbomify.com/CVE-2009-4137/): Deserialization in n/a (high 7.5)
- [CVE-2011-4941](https://insights.sbomify.com/CVE-2011-4941/): Piwik (now Matomo) Vulnerable to Arbitrary Code Execution (medium 6.8)
- [CVE-2010-2786](https://insights.sbomify.com/CVE-2010-2786/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4140 is a high-severity vulnerability in n/a, published on 22 Dec 2009. Any signed-in user can exploit it 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-4140 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-4140/ (Markdown: https://insights.sbomify.com/CVE-2009-4140/index.md)
```

## Sources

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

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