WordPress security changelog
HIGH CVE-2024-3562 Modified

Custom Field Suite: Code execution

Custom Field Suite is affected by code execution. Exploitation requires at least contributor-level access. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Custom Field Suite
Plugin slug
custom-field-suite
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jun 20, 2024
Weakness
CWE-95 — Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
CWE-94 — Improper Control of Generation of Code ('Code Injection')

This CVE was published Jun 20, 2024 and is one of 8 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Custom Field Suite to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources