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

> Remote attackers with admin access can execute arbitrary code by uploading malicious files via the File Manager in Symphony CMS.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cfxx-rjmh-m6qv

## What is CVE-2008-3592?

CVE-2008-3592 is a high-severity vulnerability in n/a, published on 11 Aug 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the File Manager in the admin panel in Twentyone Degrees Symphony 1.7.01 and earlier allows remote attackers to execute arbitrary code by uploading a file with an executable extension to a directory specified in the destination parameter, then accessing the uploaded file via a direct request, as demonstrated using workspace/masters/.

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

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

It affects 1 product.


Products: 21degrees Symphony.

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

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

## Is CVE-2008-3592 being exploited?

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

Public exploit code:

- Symphony 1.7.01 (non-patched) - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3591](https://insights.sbomify.com/CVE-2008-3591/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3592 is a high-severity vulnerability in n/a, published on 11 Aug 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3592 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-3592/ (Markdown: https://insights.sbomify.com/CVE-2008-3592/index.md)
```

## Sources

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

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