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

> WonderCMS allows uploading files with arbitrary extensions, enabling attackers to upload malicious scripts and execute code on the server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 26 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-35x3-rj44-584q

## What is CVE-2017-14521?

CVE-2017-14521 is a high-severity vulnerability in n/a, published on 26 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In WonderCMS 2.3.1, the upload functionality accepts random application extensions and leads to malicious File Upload.

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

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

It affects 1 product.


Products: Wondercms Wondercms.

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

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

## Is CVE-2017-14521 being exploited?

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

Public exploit code:

- Wonder CMS 2.3.1 - Unrestricted File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-35313](https://insights.sbomify.com/CVE-2020-35313/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-35314](https://insights.sbomify.com/CVE-2020-35314/): Code injection in n/a (critical 9.8)
- [CVE-2014-8704](https://insights.sbomify.com/CVE-2014-8704/): Path traversal in n/a (critical 9.8)
- [CVE-2014-8705](https://insights.sbomify.com/CVE-2014-8705/): Code injection in n/a (critical 9.8)
- [CVE-2024-32340](https://insights.sbomify.com/CVE-2024-32340/): Cross-site scripting in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14521 is a high-severity vulnerability in n/a, published on 26 Jan 2018. 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-2017-14521 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-2017-14521/ (Markdown: https://insights.sbomify.com/CVE-2017-14521/index.md)
```

## Sources

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

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