# CVE-2017-1002002: File upload in webapp-builder

> The WebApp Builder WordPress plugin includes vulnerable third-party software allowing attackers to upload malicious files and execute code.

- **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:** 14 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8wg4-jfmv-22fp

## What is CVE-2017-1002002?

CVE-2017-1002002 is a critical vulnerability in Invedion webapp-builder, published on 14 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in wordpress plugin webapp-builder v2.0, The plugin includes unlicensed vulnerable CMS software from http://www.invedion.com/

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

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

It affects 1 product.


Products: Webapp-Builder Project Webapp-Builder.

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

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

## Is CVE-2017-1002002 being exploited?

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

Public exploit code:

- Multiple WordPress Plugins - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1002002 is a critical vulnerability in Invedion webapp-builder, published on 14 Sep 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-1002002 in the wild and no public exploit code.

Affected product: Invedion webapp-builder. 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-1002002/ (Markdown: https://insights.sbomify.com/CVE-2017-1002002/index.md)
```

## Sources

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

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