# CVE-2017-16949: File upload in n/a

> Attackers can bypass file extension restrictions to upload malicious PHP files, leading to remote code execution on the server.

- **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:** 18 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-76m2-6qg3-g4x6

## What is CVE-2017-16949?

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

### Official description

An issue was discovered in the AccessKeys AccessPress Anonymous Post Pro plugin through 3.1.9 for WordPress. Improper input sanitization allows the attacker to override the settings for allowed file extensions and upload file size, related to inc/cores/file-uploader.php and file-uploader/file-uploader-class.php. This allows the attacker to upload anything they want to the server, as demonstrated by an action=ap_file_upload_action&allowedExtensions[]=php request to /wp-admin/admin-ajax.php that results in a .php file upload and resultant PHP code execution.

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

## Which versions are affected by CVE-2017-16949?

It affects 1 product.


Products: Accesspressthemes Anonymous Post Pro.

## How do I fix CVE-2017-16949?

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

## Is CVE-2017-16949 being exploited?

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

Public exploit code:

- Accesspress Anonymous Post Pro < 3.2.0 - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16949 and fix it if it is affected.

What it is: CVE-2017-16949 is a critical vulnerability in n/a, published on 18 Dec 2017. 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-2017-16949 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-2017-16949/ (Markdown: https://insights.sbomify.com/CVE-2017-16949/index.md)
```

## Sources

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

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