Contact Form by Supsystic <= 1.7.28 - Authenticated (Admin+) Remote Code Execution
Strategic Overview
- Status
- Patched in 1.7.29
- Affected Plugin
- Contact Form by Supsystic
- Affected Version
<= 1.7.28- CVSS
- 7.2High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2024-48042
At a glance
CVE-2024-48042 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Contact Form by Supsystic WordPress plugin, affecting versions <= 1.7.28. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.7.29; sites on affected versions should update now. Disclosed October 2024, reported by Hakiduck.
Vulnerability Overview
The Contact Form by Supsystic plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.7.28. This is due to the functionality being vulnerable to server-side template injection (SSTI). This makes it possible for authenticated attackers, with administrator-level access and above, to execute code on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Contact Form by Supsystic <= 1.7.28 takes an account at Admin level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Contact Form by Supsystic the fix is 1.7.29: builds <= 1.7.28 are affected, anything from 1.7.29 onward is not.
Remediation
Update to version 1.7.29, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Contact Form by Supsystic 1.7.29 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Contact Form by Supsystic
- 8.8Contact Form by Supsystic <= 1.7.10 SQL Injections
- 7.2CVE-2026-83625: Contact Form by Supsystic <= 1.10.2 Stored XSS
CVE-2026-83625 - 7.2CVE-2026-73378: Contact Form by Supsystic < 1.10.0 Stored XSS
CVE-2026-73378 - 6.1CVE-2025-52753: Contact Form by Supsystic <= 1.7.36 Reflected XSS
CVE-2025-52753 - 6.1CVE-2024-13452: Contact Form by Supsystic CSRF
CVE-2024-13452 - 6.1CVE-2021-24276: Contact Form by Supsystic <= 1.7.14 Reflected XSS
CVE-2021-24276 - 5.5Contact Form by Supsystic < 1.7.20 Stored Cross-Site Scripting
- 5.4CVE-2023-2528: Contact Form by Supsystic <= 1.7.24 CSRF
CVE-2023-2528
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C