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

> Authenticated authors can execute arbitrary code by uploading files with non-standard executable extensions due to an incomplete blacklist.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 6 Sep 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hv36-f2fr-5259

## What is CVE-2012-1468?

CVE-2012-1468 is a medium-severity vulnerability in n/a, published on 6 Sep 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incomplete blacklist vulnerability in Open Journal Systems before 2.3.7 allows remote authenticated users with the Author Role permission to execute arbitrary code by uploading a file with an executable extension that is not ".php", then accessing it via a direct request to the file in submission/original/ in the associated article directory, as demonstrated using .pHp, .asp, and other extensions.

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

It affects 1 product.


Products: Pkp Open Journal Systems.

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

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

## Is CVE-2012-1468 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1468 exists.

Public exploit code:

- Open Journal Systems (OJS) 2.3.6 - Multiple Script Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-1467](https://insights.sbomify.com/CVE-2012-1467/): Path traversal in n/a (medium 6.5)
- [CVE-2012-1469](https://insights.sbomify.com/CVE-2012-1469/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1468 is a medium-severity vulnerability in n/a, published on 6 Sep 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1468 exists.

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-1468/ (Markdown: https://insights.sbomify.com/CVE-2012-1468/index.md)
```

## Sources

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

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