dbcve.org
Custom Field SuiteWordPress extension · Custom Field Suite Project

CVE-2024-3562

HIGH · 8.8 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to after 2.6.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Custom Field Suite WordPress plugin has a PHP code injection vulnerability in the Loop custom field feature. Due to insufficient input sanitization, user-controlled input from the Loop custom field is passed to the PHP eval() function without proper validation, allowing authenticated attackers with contributor-level or higher permissions to execute arbitrary PHP code on the server.

MitigationUpdate the Custom Field Suite plugin to version 2.6.8 or later to receive the security patch that addresses the eval() sanitization issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Field SuiteWordPress extension
Affected:<= 2.6.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Custom Field Suite plugin is installed
    Check for the presence of the custom-field-suite directory in wp-content/plugins/ or look for 'Custom Field Suite' in the WordPress plugins admin panel at /wp-admin/plugins.php
    Affected if The plugin is installed and active on the WordPress site
  2. Check installed plugin version
    Open the main plugin file (custom-field-suite.php) in wp-content/plugins/custom-field-suite/ and locate the Version header in the plugin comment block, or check the plugins admin page for the installed version number
    Affected if The installed version is 2.6.7 or lower (any version <= 2.6.7)
  3. Identify if Loop custom field type is in use
    Examine WordPress database tables (typically wp_options or custom tables created by the plugin) for field group configurations containing the 'loop' field type, or check plugin settings for any defined Loop fields
    Affected if Any Loop custom field is defined or configured in the plugin's field groups
  4. Check foreval() usage in plugin files
    Search the custom-field-suite plugin directory for eval( statements, particularly in files related to field processing (loop.php, field-loop.php, or similar field-type files)
    Affected if The plugin code contains eval() calls handling Loop field input without sanitization

A site is affected if Custom Field Suite plugin version 2.6.7 or lower is installed AND the Loop custom field feature is actively used, allowing authenticated users with contributor-level or higher permissions to inject arbitrary PHP code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.6.7
Interim mitigation

Update the Custom Field Suite plugin to version 2.6.8 or later to receive the security patch that addresses the eval() sanitization issue.

Recommended fix High confidence

Custom Field Suite 2.6.8

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate Custom Field Suite in the plugin list
  3. Click 'Update now' if an update is available, or manually update to version 2.6.8 or higher
  4. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Custom Field Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3562 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data