HomeWordPress vulnerabilitiesSmart Custom Fields
Smart Custom Fields vulnerabilities
Smart Custom Fields has 3 known vulnerabilities in this database. The most recent published record is dated 17 Jul 2026.
- Known vulnerabilities
- 3
- Active installs
- 50,000+
- Latest version
- 5.0.8
- Last updated
- 16 Jul 2026
- Most recent
- 17 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-2594 | Medium 6.4 | Up to 5.0.7 | Fixed in a later version (latest 5.0.8) | 17 Jul 2026 |
| Broken access control CVE-2026-4066 | Medium 4.3 | Up to 5.0.6 | Fixed in a later version (latest 5.0.8) | 23 Mar 2026 |
| Broken access control CVE-2024-1995 | Medium 4.3 | Up to 4.2.2 | Fixed in a later version (latest 5.0.8) | 20 Mar 2024 |
Read the published descriptions
- CVE-2026-2594, 17 Jul 2026
- The Smart Custom Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.7. This is due to insufficient input sanitization and output escaping of uploaded image attachment titles. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: This vulnerability was partially patched in 5.0.7. CVE record
- CVE-2026-4066, 23 Mar 2026
- The Smart Custom Fields plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the relational_posts_search() function in all versions up to, and including, 5.0.6. This makes it possible for authenticated attackers, with Contributor-level access and above, to read private and draft post content from other authors via the smart-cf-relational-posts-search AJAX action. The function queries posts with post_status=any and returns full WP_Post objects including post_content, but only checks the generic edit_posts capability instead of verifying whether the requesting user has permission to read each individual post. CVE record
- CVE-2024-1995, 20 Mar 2024
- The Smart Custom Fields plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the relational_posts_search() function in all versions up to, and including, 4.2.2. This makes it possible for authenticated attackers, with subscrber-level access and above, to retrieve post content that is password protected and/or private. CVE record
What to do if you run Smart Custom Fields
If you run Smart Custom Fields, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Smart Custom Fields vulnerabilities
Free. We email you when a new vulnerability is published for Smart Custom Fields, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.