# CVE-2015-1172: File upload in n/a

> Remote attackers with admin privileges can execute arbitrary PHP code by uploading malicious files to the Holding Pattern WordPress theme.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fv4f-gcrq-728w

## What is CVE-2015-1172?

CVE-2015-1172 is a high-severity vulnerability in n/a, published on 11 Feb 2015. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in admin/upload-file.php in the Holding Pattern theme (aka holding_pattern) 0.6 and earlier for WordPress allows remote attackers to execute arbitrary PHP code by uploading a file with a PHP extension, then accessing it via a direct request to the file in an unspecified directory.

## Which versions are affected by CVE-2015-1172?

It affects 1 product.


Products: Holding Pattern Project Holding Pattern.

## How do I fix CVE-2015-1172?

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

## Is CVE-2015-1172 being exploited?

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

Public exploit code:

- WordPress Theme Holding Pattern - Arbitrary File Upload (Metasploit) (exploitdb)
- WordPress Holding Pattern Theme Arbitrary File Upload (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1172 and fix it if it is affected.

What it is: CVE-2015-1172 is a high-severity vulnerability in n/a, published on 11 Feb 2015. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1172 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-2015-1172/ (Markdown: https://insights.sbomify.com/CVE-2015-1172/index.md)
```

## Sources

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

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