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

> Authenticated attackers can upload arbitrary files to the server, potentially leading to remote code execution.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 14 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mp4p-8xg5-v566

## What is CVE-2008-2216?

CVE-2008-2216 is a critical vulnerability in n/a, published on 14 May 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in src/yopy_upload.php in Project-Based Calendaring System (PBCS) 0.7.1 allows remote authenticated users to upload arbitrary files to tmp/uploads.

Weakness: CWE-264

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

It affects 1 product.


Products: Pbcs Project-Based Calendaring  System.

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

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

## Is CVE-2008-2216 being exploited?

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

Public exploit code:

- Project Based Calendaring System (PBCS) 0.7.1 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-2215](https://insights.sbomify.com/CVE-2008-2215/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2216 is a critical vulnerability in n/a, published on 14 May 2008. 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-2008-2216 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-2216/ (Markdown: https://insights.sbomify.com/CVE-2008-2216/index.md)
```

## Sources

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

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