# CVE-2007-4817: File upload in n/a

> Remote attackers can upload and execute arbitrary PHP code via double-extension filenames in the Joomla! Restaurante component.

- **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:** 11 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h5jv-54pc-fqch

## What is CVE-2007-4817?

CVE-2007-4817 is a high-severity vulnerability in n/a, published on 11 Sep 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the Restaurante (com_restaurante) component for Joomla! allows remote attackers to upload and execute arbitrary PHP code via an upload action specifying a filename with a double extension such as .php.jpg, which creates an accessible file under img_original/.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2007-4817?

It affects 1 product.


Products: Detodas Restaurante Component for Joomla.

## How do I fix CVE-2007-4817?

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

## Is CVE-2007-4817 being exploited?

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

Public exploit code:

- Joomla! Component Restaurante - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4817 and fix it if it is affected.

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

## Sources

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

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