# CVE-2008-7215: File upload in n/a

> Remote attackers can rename arbitrary files and cause denial of service in MOStlyCE Image Manager by manipulating upload parameters.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/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 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-938c-gh9h-4wpx

## What is CVE-2008-7215?

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

### Official description

The Image Manager in MOStlyCE before 2.4, as used in Mambo 4.6.3 and earlier, allows remote attackers to rename arbitrary files and cause a denial of service via modified file[NewFile][name], file[NewFile][tmp_name], and file[NewFile][size] parameters in a FileUpload command, which are used to modify equivalent variables in $_FILES that are accessed when the is_uploaded_file check fails.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-7215?

It affects 2 products.


Products: Brilaps Mostlyce, Mambo-Foundation Mambo.

## How do I fix CVE-2008-7215?

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

## Is CVE-2008-7215 being exploited?

There is no known exploitation of CVE-2008-7215 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-7214](https://insights.sbomify.com/CVE-2008-7214/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2008-7212](https://insights.sbomify.com/CVE-2008-7212/): Information disclosure in n/a (medium 5.0)
- [CVE-2008-7213](https://insights.sbomify.com/CVE-2008-7213/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7215 and fix it if it is affected.

What it is: CVE-2008-7215 is a medium-severity vulnerability in n/a, published on 11 Sep 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-7215 in the wild and no public exploit code.

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-2008-7215/ (Markdown: https://insights.sbomify.com/CVE-2008-7215/index.md)
```

## Sources

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

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