# CVE-2024-50523: WordPress All Post Contact Form plugin <= 1.8.2 - Arbitrary File Upload vulnerability

> An attacker can upload a malicious web shell to the server, leading to remote code execution on sites using the All Post Contact Form plugin.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 4 Nov 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-f9j4-243j-7p57

## What is CVE-2024-50523?

CVE-2024-50523 is a critical vulnerability in RainbowLink Inc. All Post Contact Form, published on 4 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in RainbowLink Inc. All Post Contact Form allpost-contactform allows Upload a Web Shell to a Web Server.This issue affects All Post Contact Form: from n/a through <= 1.8.2.

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

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

It affects 1 product.


Products: Rainbow-Link All Post Contact Form.

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

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

## Is CVE-2024-50523 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50523 is a critical vulnerability in RainbowLink Inc. All Post Contact Form, published on 4 Nov 2024. 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-2024-50523 in the wild and no public exploit code.

Affected product: RainbowLink Inc. All Post Contact Form. 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-50523/ (Markdown: https://insights.sbomify.com/CVE-2024-50523/index.md)
```

## Sources

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

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