Custom Field Suite vulnerabilities

Plugin slug custom-field-suite · 9 known vulnerabilities · latest disclosed 2024-06-19 · WordPress.org page

4 vulnerabilities have no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.

2 of 9 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Custom Field Suite

SeverityAffected versionsFixed inCVEPublishedDetails
Medium 6.4<= 2.6.7No fix yetCVE-2024-35582024-06-19Advisory
High 8.8<= 2.6.7No fix yetCVE-2024-35622024-06-19Advisory
High 8.8<= 2.6.7No fix yetCVE-2024-35612024-06-19Advisory
Medium 6.4<= 2.6.7No fix yetCVE-2024-35592024-06-11Advisory
Medium 4.4<= 2.6.52.6.6CVE-2024-30682024-05-07Advisory
Medium 4.4<= 2.6.42.6.5CVE-2024-06892024-02-28Advisory
Medium 4.4<= 2.6.2.12.6.3CVE-2023-325152023-05-10Advisory
Medium 5.4<= 2.5.142.5.15CVE-2019-118712019-05-08Advisory
Medium 6.3<= 2.42.4.1none2015-03-12Advisory

Check if a site is affected

Enter a site address to see which version of Custom Field Suite and other plugins it runs, and whether they match a known vulnerability.

Questions

Is the Custom Field Suite plugin safe to use?

4 known issue(s) have no fix yet, so check the table above before using it.

How do I check which version of Custom Field Suite my site runs?

In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.

How do I fix a vulnerable plugin?

Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.

Check any WordPress site in one click while you browse: Add PluginPeek to Chrome