# CVE-2012-5318: File upload in n/a

> Remote attackers can execute arbitrary code by uploading malicious files with double extensions in the Kish Guest Posting WordPress plugin.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g56r-2vjm-9c6p

## What is CVE-2012-5318?

CVE-2012-5318 is a medium-severity vulnerability in n/a, published on 8 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in uploadify/scripts/uploadify.php in the Kish Guest Posting plugin 1.2 for WordPress allows remote attackers to execute arbitrary code by uploading a file with a double extension, then accessing it via a direct request to the file in the directory specified by the folder parameter.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-1125.

## Which versions are affected by CVE-2012-5318?

It affects 1 product.


Products: Kishore Asokan Kish Guest Posting Plugin.

## How do I fix CVE-2012-5318?

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

## Is CVE-2012-5318 being exploited?

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

Public exploit code:

- WordPress Plugin Kish Guest Posting 1.0 - Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-1125](https://insights.sbomify.com/CVE-2012-1125/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5318 and fix it if it is affected.

What it is: CVE-2012-5318 is a medium-severity vulnerability in n/a, published on 8 Oct 2012. 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-2012-5318 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-2012-5318/ (Markdown: https://insights.sbomify.com/CVE-2012-5318/index.md)
```

## Sources

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

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