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

> Authenticated users can upload malicious files to execute arbitrary code on the Zeeways ZEEJOBSITE web application.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/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 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vf8g-xc3c-j27h

## What is CVE-2008-6913?

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

### Official description

Unrestricted file upload vulnerability in editresume_next.php in Zeeways ZEEJOBSITE 2.0 allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension as a photo in a profile edit action, then accessing the file via a direct request to jobseekers/logos/.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Zeeways Zeejobsite.

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

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

## Is CVE-2008-6913 being exploited?

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

Public exploit code:

- Zeeways ZeeJobsite 2.0 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3706](https://insights.sbomify.com/CVE-2008-3706/): SQL injection in n/a (high 7.5)
- [CVE-2009-4601](https://insights.sbomify.com/CVE-2009-4601/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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