# CVE-2024-48042: WordPress Contact Form by Supsystic plugin <= 1.7.28 - Remote Code Execution (RCE) vulnerability

> Attackers can achieve remote code execution via unsafe deserialization in the Contact Form by Supsystic WordPress plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-h9vw-g3h9-6jvw

## What is CVE-2024-48042?

CVE-2024-48042 is a critical unsafe deserialization vulnerability in Contact Form by Supsystic, published on 16 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Deserialization of Untrusted Data vulnerability in supsystic Contact Form by Supsystic contact-form-by-supsystic allows Command Injection.This issue affects Contact Form by Supsystic: from n/a through <= 1.7.28.

Weakness: CWE-82 (Improper Neutralization of Script in Attributes of IMG Tags in a Web Page)

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


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

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

## Is CVE-2024-48042 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48042 is a critical unsafe deserialization vulnerability in Contact Form by Supsystic, published on 16 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48042 in the wild and no public exploit code.

Affected product: Contact Form by Supsystic. 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-48042/ (Markdown: https://insights.sbomify.com/CVE-2024-48042/index.md)
```

## Sources

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

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