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

> Remote attackers can execute arbitrary code by uploading malicious files with executable extensions in the Aviary Image Editor plugin for WordPress.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-548f-66xm-vfq4

## What is CVE-2015-4455?

CVE-2015-4455 is a critical vulnerability in n/a, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in includes/upload.php in the Aviary Image Editor Add-on For Gravity Forms plugin 3.0 beta for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in wp-content/uploads/gform_aviary.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Aviary Image Editor Add-on for Gravity Forms Project Aviary Image Editor Add-on for Gravity Forms.

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

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

## Is CVE-2015-4455 being exploited?

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

Public exploit code:

- WordPress Plugin Aviary Image Editor Addon For Gravity Forms 3.0 Beta - Arbitrary File Upload (exploitdb)
- WordPress Plugin Aviary Image Editor Addon For Gravity Forms 3.0 Beta - Arbitrary File Upload (nuclei): http/cves/2015/CVE-2015-4455.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4455 is a critical vulnerability in n/a, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-4455 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-4455/ (Markdown: https://insights.sbomify.com/CVE-2015-4455/index.md)
```

## Sources

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

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