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

> Authenticated administrators can upload and execute arbitrary PHP files in EncapsGallery, 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q876-9whr-9j9w

## What is CVE-2008-1988?

CVE-2008-1988 is a critical vulnerability in n/a, published on 27 Apr 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in the file_upload function in core/misc.class.php in EncapsGallery 2.0.2 allows remote authenticated administrators to upload and execute arbitrary PHP files by uploading a file with an executable extension, then accessing it via a direct request to the file in the rwx_gallery directory.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Encaps Encapsgallery.

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

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

## Is CVE-2008-1988 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1987](https://insights.sbomify.com/CVE-2008-1987/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-1296](https://insights.sbomify.com/CVE-2008-1296/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1988 is a critical vulnerability in n/a, published on 27 Apr 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1988 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-1988/ (Markdown: https://insights.sbomify.com/CVE-2008-1988/index.md)
```

## Sources

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

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