# CVE-2005-4800: Code injection in n/a

> Authenticated administrators can inject arbitrary PHP code via the TestGallery parameter, 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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2006
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gv3m-j4wj-2r64

## What is CVE-2005-4800?

CVE-2005-4800 is a critical code injection vulnerability in n/a, published on 15 May 2006. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Direct static code injection vulnerability in Yet Another PHP Image Gallery (YaPIG) 0.95b and earlier allows remote authenticated administrators to inject arbitrary PHP code via the TestGallery parameter in a mod_info action to modify_gallery.php, which inserts the code into guid_info.php.  NOTE: this issue is easier to exploit due to a separate CSRF vulnerability.

## Which versions are affected by CVE-2005-4800?

It affects 1 product.


Products: Yapig Yapig.

## How do I fix CVE-2005-4800?

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

## Is CVE-2005-4800 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4801](https://insights.sbomify.com/CVE-2005-4801/): Cross-site request forgery in n/a (high 7.5)
- [CVE-2005-1881](https://insights.sbomify.com/CVE-2005-1881/): File upload in n/a (high 7.5)
- [CVE-2005-1882](https://insights.sbomify.com/CVE-2005-1882/): Code injection in n/a (high 7.5)
- [CVE-2007-4951](https://insights.sbomify.com/CVE-2007-4951/): Code injection in n/a (medium 6.8)
- [CVE-2005-1884](https://insights.sbomify.com/CVE-2005-1884/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4800 and fix it if it is affected.

What it is: CVE-2005-4800 is a critical code injection vulnerability in n/a, published on 15 May 2006. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-4800 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-2005-4800/ (Markdown: https://insights.sbomify.com/CVE-2005-4800/index.md)
```

## Sources

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

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