Is custom-field-suite (WordPress plugin) vulnerable?

WordPress custom-field-suite has 7 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

7advisories
0critical
0on CISA KEV
4no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-11871The Custom Field Suite plugin before 2.5.15 for WordPress has XSS for editors or admins.medium5.4<2.5.152.5.15
CVE-2024-3562The 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 cushigh8.8<=2.6.7–
CVE-2024-3068The Custom Field Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cfs[fields][*][name]' parameter in all vermedium4.4<2.6.62.6.6
CVE-2024-3561The Custom Field Suite plugin for WordPress is vulnerable to SQL Injection via the the 'Term' custom field in all versions up to, and includhigh8.8<=2.6.7–
CVE-2024-3558The Custom Field Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the the 'cfs[post_title]' parameter versions upmedium6.4<=2.6.7–
CVE-2024-0689The Custom Field Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via a meta import in all versions up to, and includmedium4.4<2.6.52.6.5
CVE-2024-3559The Custom Field Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the the 'cfs[post_content]' parameter versions medium6.4<=2.6.7–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.