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

> Remote attackers can execute arbitrary code by uploading a malicious PHP file via the loadsave.php script in Flux CMS.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 13 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-729q-v478-ggh5

## What is CVE-2008-2686?

CVE-2008-2686 is a high-severity vulnerability in n/a, published on 13 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

webinc/bxe/scripts/loadsave.php in Flux CMS 1.5.0 and earlier allows remote attackers to execute arbitrary code by overwriting a PHP file in webinc/bxe/scripts/ via a filename in the XML parameter and PHP sequences in the request body, then making a direct request for this filename.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Flux Cms Flux Cms.

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

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

## Is CVE-2008-2686 being exploited?

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

Public exploit code:

- Flux CMS 1.5.0 - 'loadsave.php' Arbitrary File Overwrite (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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