# CVE-2024-50427: WordPress SurveyJS plugin <= 1.9.136 - Arbitrary File Upload vulnerability

> Attackers can upload malicious files to the SurveyJS WordPress plugin, potentially leading to remote code execution on the server.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 29 Oct 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8gp9-7p8q-9846

## What is CVE-2024-50427?

CVE-2024-50427 is a critical vulnerability in devsoftbaltic SurveyJS, published on 29 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in devsoftbaltic SurveyJS surveyjs.This issue affects SurveyJS: from n/a through <= 1.9.136.

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

## Which versions are affected by CVE-2024-50427?


## How do I fix CVE-2024-50427?

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

## Is CVE-2024-50427 being exploited?

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

Public exploit code:

- SurveyJS: Drag & Drop WordPress Form Builder <= 1.9.136 - Authenticated (Subscriber+) Arbitrary File Upload (github_poc): https://github.com/RandomRobbieBF/CVE-2024-50427

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50427 and fix it if it is affected.

What it is: CVE-2024-50427 is a critical vulnerability in devsoftbaltic SurveyJS, published on 29 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50427 in the wild and no public exploit code.

Affected product: devsoftbaltic SurveyJS. 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-2024-50427/ (Markdown: https://insights.sbomify.com/CVE-2024-50427/index.md)
```

## Sources

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

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