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

> Remote attackers can execute arbitrary code by including malicious files via the conf_path parameter in the Yawp library.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pr8q-f7jx-h4v7

## What is CVE-2005-2319?

CVE-2005-2319 is a medium-severity vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file include vulnerability in Yawp library 1.0.6 and earlier, as used in YaWiki and possibly other products, allows remote attackers to include arbitrary files via the _Yawp[conf_path] parameter.

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

It affects 1 product.


Products: Yawp Yawp.

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

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

## Is CVE-2005-2319 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2319 is a medium-severity vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2319 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-2319/ (Markdown: https://insights.sbomify.com/CVE-2005-2319/index.md)
```

## Sources

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

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