CFS Options Screens Security & Risk Analysis

wordpress.org/plugins/cfs-options-screens

Create options screens that utilize Custom Field Suite

400 active installs v1.2.7 PHP + WP 3.9+ Updated Feb 10, 2022
cfscustom-field-suiteoptionsscreensettings
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is CFS Options Screens Safe to Use in 2026?

Generally Safe

Score 85/100

CFS Options Screens has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

The "cfs-options-screens" v1.2.7 plugin exhibits a strong security posture based on the provided static analysis. It demonstrates excellent adherence to secure coding practices, with no identified dangerous functions, all SQL queries using prepared statements, and all output properly escaped. The absence of file operations and external HTTP requests further reduces potential attack vectors. Crucially, there are no AJAX handlers, REST API routes, shortcodes, or cron events exposed, resulting in a minimal attack surface with zero entry points, let alone unprotected ones.

The vulnerability history is equally positive, with zero known CVEs recorded for this plugin. This, combined with the clean static analysis, suggests a well-maintained and secure plugin. The lack of any recorded vulnerabilities, including common types, over time indicates a consistent focus on security by the developers or a lack of significant exposure that has led to discovered issues.

Overall, "cfs-options-screens" v1.2.7 appears to be a highly secure plugin. The complete absence of critical or high-severity findings in both static analysis and vulnerability history, coupled with the minimal attack surface, paints a picture of a robustly developed and maintained piece of software. While the lack of nonce and capability checks on the zero entry points might seem like a concern in isolation, given that there are no entry points, this does not pose a practical risk. The plugin's strengths lie in its clean code and unblemished security record.

Vulnerabilities
None known

CFS Options Screens Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

CFS Options Screens Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
17 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

100% escaped17 total outputs
Attack Surface

CFS Options Screens Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actioninitcfs-options-screens.php:60
actionadmin_print_scriptscfs-options-screens.php:61
actioncfs_matching_groupscfs-options-screens.php:63
actioncfs_form_before_fieldscfs-options-screens.php:64
actionadmin_enqueue_scriptscfs-options-screens.php:174
actionadmin_noticescfs-options-screens.php:177
actionadmin_menucfs-options-screens.php:192
Maintenance & Trust

CFS Options Screens Maintenance & Trust

Maintenance Signals

WordPress version tested5.9.0
Last updatedFeb 10, 2022
PHP min version
Downloads7K

Community Trust

Rating100/100
Number of ratings2
Active installs400
Developer Profile

CFS Options Screens Developer Profile

Jon Christopher

11 plugins · 110K total installs

86
trust score
Avg Security Score
89/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect CFS Options Screens

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/cfs-options-screens/style.css
Version Parameters
cfs-options-screens/style.css?ver=

HTML / DOM Fingerprints

CSS Classes
cfs-options-screens-note
FAQ

Frequently Asked Questions about CFS Options Screens