# CVE-2005-4814: File upload in n/a

> Remote attackers can upload and execute arbitrary PHP code via .phtml files in Segue CMS if Apache is configured to process them.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 31 Oct 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p37h-9c34-5f75

## What is CVE-2005-4814?

CVE-2005-4814 is a high-severity vulnerability in n/a, published on 31 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in Segue CMS before 1.3.6, when the Apache HTTP Server handles .phtml files with the PHP interpreter, allows remote attackers to upload and execute arbitrary PHP code by placing .phtml files in the userfiles/ directory.

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

It affects 1 product.


Products: Middlebury College Segue Cms.

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

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

## Is CVE-2005-4814 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5490](https://insights.sbomify.com/CVE-2006-5490/): SQL injection in n/a (high 7.5)
- [CVE-2006-5497](https://insights.sbomify.com/CVE-2006-5497/): Code injection in n/a (high 7.5)
- [CVE-2006-5498](https://insights.sbomify.com/CVE-2006-5498/): Path traversal in n/a (high 7.5)
- [CVE-2006-5722](https://insights.sbomify.com/CVE-2006-5722/): Code injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4814 is a high-severity vulnerability in n/a, published on 31 Oct 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4814 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-4814/ (Markdown: https://insights.sbomify.com/CVE-2005-4814/index.md)
```

## Sources

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

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