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

CVE-2024-3559

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to after 2.6.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Stored Cross-Site Scripting via the the 'cfs[post_content]' parameter versions up to, and including, 2.6.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 fails to properly sanitize the cfs[post_content] parameter during input and escape it during output, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript that persists in the database and executes when other users view affected pages.

MitigationUpdate Custom Field Suite to the latest version which implements proper input sanitization using functions like sanitize_text_field and output escaping with esc_html or esc_attr. If immediate update is not possible, restrict contributor-level user permissions until the patch can be applied.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Custom Field Suite' in the list. Note if it is active or inactive.
    Affected if Plugin is installed and active - inactive installations are not affected since the vulnerable code cannot be executed
  2. Check installed plugin version
    Click 'View details' on the Custom Field Suite plugin in the WordPress plugins list, or check the plugin's main PHP file header for the Version: X.X.X entry. Compare against the affected range: <= 2.6.7
    Affected if Version number is 2.6.7 or lower
  3. Identify user accounts with contributor-level permissions or higher
    In WordPress admin, go to Users > All Users and review the Role column. Users listed as Contributor, Author, Editor, or Administrator can exploit this vulnerability.
    Affected if At least one user account has Contributor, Author, Editor, or Administrator role
  4. Check if the plugin's post_content field is in use
    Navigate to Field Groups in the WordPress admin (CFS menu > Field Groups). Review each field group for fields named 'post_content' or similar content fields that store data to the post_content meta key.
    Affected if A CFS field group contains a field that saves to the cfs[post_content] meta key or similar content field

User is affected if Custom Field Suite plugin version 2.6.7 or lower is active AND at least one Contributor-level or higher user account exists in WordPress AND the plugin's post_content field is being used in a field group.

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.

From vendor data
Upgrade available Upgrade to a release after 2.6.7
Interim mitigation

Update Custom Field Suite to the latest version which implements proper input sanitization using functions like sanitize_text_field and output escaping with esc_html or esc_attr. If immediate update is not possible, restrict contributor-level user permissions until the patch can be applied.

Fix this in Custom Field Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3559 — 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-3559 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