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

> Authenticated attackers can upload malicious files to execute arbitrary code on AvailScript Jobs Portal Script servers.

- **Severity:** Medium 6.0 (`AV:N/AC:M/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:** 21 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cqp9-hhmj-77gv

## What is CVE-2008-7021?

CVE-2008-7021 is a medium-severity vulnerability in n/a, published on 21 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 editlogo.php in AvailScript Jobs Portal Script allows remote authenticated users to execute arbitrary code by uploading a file with an executable extension as an image or logo, then accessing it via a direct request to the file in an unspecified directory.

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

It affects 1 product.


Products: Availscript Jobs Portal Script.

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

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

## Is CVE-2008-7021 being exploited?

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

Public exploit code:

- AvailScript Jobs Portal Script - (Authenticated) Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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