Is Secure Custom Fields safe?

No known vulnerability affects the current version (6.9.8). 1 issue was found in earlier versions and fixed, the latest disclosed on Sep 19, 2026.

Checked 5 days ago against the WPVulnerability database, for version 6.9.8.

How it’s looked after

Last release: Nov 3, 2026 (5 days ago)
Releases in the last year: 22
Tested up to: WordPress 7.1.4
Support resolved: 1 of 5 threads in two months
Active installs: 100K+

1 known vulnerability

1 not rated

None affects the current version.

Every known vulnerability in Secure Custom Fields

Newest first, with any that affect the current version at the top.

Missing Authorization
Fixed in 6.9.4 · CVE-2026-92403 · Sep 19, 2026 · Wordfence

Questions about Secure Custom Fields’s security

Is Secure Custom Fields safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Secure Custom Fields updated: most attacks target sites that haven’t updated.

Does Secure Custom Fields have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Secure Custom Fields up to date.

Is Secure Custom Fields still maintained?

Yes. Its last release was 5 days ago. Its authors resolved 1 of the 5 support threads opened in the last two months.

Is Secure Custom Fields compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

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 free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.