Custom Field Suite <= 2.6.7 - Authenticated (Contributor+) PHP Code Injection via Loop Custom Field
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Custom Field Suite
- Affected Version
<= 2.6.7- CVSS
- 8.8High
- Weakness type
- CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
- CVE
CVE-2024-3562
At a glance
CVE-2024-3562 is a high-severity Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') vulnerability in the Custom Field Suite WordPress plugin, affecting versions <= 2.6.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2024, reported by Jack Taylor.
Vulnerability Overview
The Custom Field Suite plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.6.7 via the Loop custom field. This is due to insufficient sanitization of input prior to being used in a call to the eval() function. This makes it possible for authenticated attackers, with contributor-level access and above, to execute arbitrary PHP 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-95: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Contributor 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Custom Field Suite
- 8.8CVE-2024-3561: Custom Field Suite <= 2.6.7 SQL Injection
CVE-2024-3561 - 6.4CVE-2024-3558: Custom Field Suite <= 2.6.7 Stored Cross-Site Scripting
CVE-2024-3558 - 6.4CVE-2024-3559: Custom Field Suite <= 2.6.7 Stored Cross-Site Scripting
CVE-2024-3559 - 6.3Custom Field Suite <= 2.4 Missing Authorization
- 5.4CVE-2019-11871: Custom Field Suite <= 2.5.14 Cross-Site Scripting
CVE-2019-11871 - 4.4CVE-2024-3068: Custom Field Suite <= 2.6.5 Stored Cross-Site Scripting
CVE-2024-3068 - 4.4CVE-2024-0689: Custom Field Suite <= 2.6.4 Stored Cross-Site Scripting
CVE-2024-0689 - 4.4CVE-2023-32515: Custom Field Suite <= 2.6.2.1 Stored XSS
CVE-2023-32515
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C