# CVE-2014-9567: File upload in n/a

> Remote attackers can execute arbitrary PHP code by uploading malicious files to ProjectSend, leading to full system compromise.

- **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:** 7 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9wrg-v9p9-p326

## What is CVE-2014-9567?

CVE-2014-9567 is a high-severity vulnerability in n/a, published on 7 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in process-upload.php in ProjectSend (formerly cFTP) r100 through r561 allows remote attackers to execute arbitrary PHP code by uploading a file with a PHP extension, then accessing it via a direct request to the file in the upload/files/ or upload/temp/ directory.

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

## Which versions are affected by CVE-2014-9567?

It affects 1 product.


Products: Projectsend Projectsend.

## How do I fix CVE-2014-9567?

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

## Is CVE-2014-9567 being exploited?

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

Public exploit code:

- ProjectSend r-561 - Arbitrary File Upload (exploitdb)
- ProjectSend Arbitrary File Upload (metasploit)
- ProjectSend - Arbitrary File Upload (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-11680](https://insights.sbomify.com/CVE-2024-11680/): ProjectSend Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-40887](https://insights.sbomify.com/CVE-2021-40887/): Path traversal in n/a (critical 9.8)
- [CVE-2016-10731](https://insights.sbomify.com/CVE-2016-10731/): SQL injection in n/a (critical 9.8)
- [CVE-2016-10732](https://insights.sbomify.com/CVE-2016-10732/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-10733](https://insights.sbomify.com/CVE-2016-10733/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9567 and fix it if it is affected.

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

## Sources

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

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