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

> Remote attackers can execute arbitrary code by uploading executable files as user images in the Opial web application.

- **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 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xm9f-jp6r-h9h7

## What is CVE-2009-3753?

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

### Official description

Unrestricted file upload vulnerability in Opial 1.0 allows remote attackers to execute arbitrary code by uploading a file with an executable extension as a User Image, then accessing it via a request to the file in userimages, related to register.php.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Opial Opial.

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

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

## Is CVE-2009-3753 being exploited?

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

Public exploit code:

- Opial 1.0 - Arbitrary File Upload / Cross-Site Scripting / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-3752](https://insights.sbomify.com/CVE-2009-3752/): SQL injection in n/a (high 7.5)
- [CVE-2009-2340](https://insights.sbomify.com/CVE-2009-2340/): SQL injection in n/a (high 7.5)
- [CVE-2009-3751](https://insights.sbomify.com/CVE-2009-3751/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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