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

> Remote attackers with admin access can upload and execute arbitrary PHP files in Benja CMS, 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wq2c-7m9f-vjwv

## What is CVE-2008-2988?

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

### Official description

Unrestricted file upload vulnerability in admin/upload.php in Benja CMS 0.1 allows remote attackers to upload and execute arbitrary PHP files via unspecified vectors, followed by a direct request to the file in billeder/.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Benjacms Benja Cms.

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

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

## Is CVE-2008-2988 being exploited?

There is no known exploitation of CVE-2008-2988 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-2879](https://insights.sbomify.com/CVE-2008-2879/): Missing authorization in n/a (medium 6.4)
- [CVE-2008-2987](https://insights.sbomify.com/CVE-2008-2987/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2988 is a high-severity vulnerability in n/a, published on 2 Jul 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2988 in the wild and no public exploit code.

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-2988/ (Markdown: https://insights.sbomify.com/CVE-2008-2988/index.md)
```

## Sources

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

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