Smart Custom Fields · Security record
Is Smart Custom Fields safe?
No known vulnerability affects the current version (5.0.8). 4 issues were found in earlier versions and fixed, the latest disclosed on Jul 16, 2026.
Checked 5 days ago against the WPVulnerability database, for version 5.0.8.
How it’s looked after
- Last release
- Jul 16, 2026 (3 months ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Active installs
- 50K+
4 known vulnerabilities
- 3 medium
- 1 not rated
None affects the current version.
Disclosed each year
- 20241
- 20251
- 20262
Every known vulnerability in Smart Custom Fields
Newest first, with any that affect the current version at the top.
Fixed in 5.0.8 · CVE-2026-2594 · Jul 16, 2026 · Wordfence
Fixed in 5.0.7 · CVE-2026-4066 · Mar 23, 2026 · Wordfence
Fixed in 5.0.1 · CVE-2025-22308 · Jan 6, 2025 · Wordfence
Fixed in 5.0.0 · CVE-2024-1995 · Mar 19, 2024 · Wordfence
Questions about Smart Custom Fields’s security
Is Smart Custom Fields safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Smart Custom Fields updated: most attacks target sites that haven’t updated.
Does Smart Custom Fields have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Smart Custom Fields up to date.
Is Smart Custom Fields still maintained?
Yes. Its last release was 3 months ago. No support threads were opened in the last two months.
Is Smart Custom Fields compatible with the latest WordPress?
Smart Custom Fields’s readme says it’s tested up to WordPress 6.8.12, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.