Safelayout Brilliant Buttons – WordPress Buttons Security & Risk Analysis

wordpress.org/plugins/safelayout-brilliant-buttons

Beautiful CSS buttons, available for Classic Editor, Block Editor and Elementor.

50 active installs v1.2.3 PHP 7.0+ WP 6.5+ Updated Feb 26, 2026
blockbuttonbutton-blockwordpress-buttons
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Safelayout Brilliant Buttons – WordPress Buttons Safe to Use in 2026?

Generally Safe

Score 100/100

Safelayout Brilliant Buttons – WordPress Buttons has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The safelayout-brilliant-buttons plugin v1.2.3 exhibits a strong security posture based on the provided static analysis and vulnerability history. All identified entry points (AJAX handlers) appear to have proper authorization checks, and there are no indications of dangerous functions, raw SQL queries, or file operations, which are common sources of vulnerabilities. The plugin also implements nonce checks on its AJAX handlers, further strengthening its security. The lack of known CVEs and recorded vulnerabilities suggests a commitment to secure coding practices by the developers.

However, there are a few areas that warrant attention. While a significant majority of output is properly escaped, the 24% that is not could potentially lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is involved. Additionally, the presence of external HTTP requests, even if limited, introduces a dependency on external services and could be a vector for supply chain attacks if not handled securely. The absence of any taint analysis results, while positive in that no critical flows were found, could also indicate that thorough taint analysis was not performed, or the analysis tool had limitations.

In conclusion, safelayout-brilliant-buttons v1.2.3 is generally secure with good practices in place, particularly regarding authentication and SQL handling. The primary concern lies with the unescaped output, which should be remediated. The plugin benefits from a clean vulnerability history, indicating past diligence. While the current posture is good, continuous monitoring and attention to unescaped output are recommended for sustained security.

Key Concerns

  • Unescaped output detected (24%)
  • External HTTP requests present
Vulnerabilities
None known

Safelayout Brilliant Buttons – WordPress Buttons Security Vulnerabilities

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

Safelayout Brilliant Buttons – WordPress Buttons Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
8
26 escaped
Nonce Checks
3
Capability Checks
0
File Operations
0
External Requests
2
Bundled Libraries
0

Output Escaping

76% escaped34 total outputs
Attack Surface

Safelayout Brilliant Buttons – WordPress Buttons Attack Surface

Entry Points3
Unprotected0

AJAX Handlers 3

authwp_ajax_slbb_buttons_feedbacksafelayout-brilliant-buttons.php:86
authwp_ajax_slbb_buttons_upgradesafelayout-brilliant-buttons.php:478
authwp_ajax_slbb_buttons_rate_remindersafelayout-brilliant-buttons.php:482
WordPress Hooks 51
actioninitsafelayout-brilliant-buttons.php:34
actionactivated_pluginsafelayout-brilliant-buttons.php:35
filterwp_kses_allowed_htmlsafelayout-brilliant-buttons.php:37
filtersafecss_filter_attr_allow_csssafelayout-brilliant-buttons.php:38
filtersafe_style_csssafelayout-brilliant-buttons.php:39
actioninitsafelayout-brilliant-buttons.php:41
actioninitsafelayout-brilliant-buttons.php:42
actionenqueue_block_editor_assetssafelayout-brilliant-buttons.php:43
actionenqueue_block_editor_assetssafelayout-brilliant-buttons.php:44
filterblock_categories_allsafelayout-brilliant-buttons.php:45
filtertiny_mce_before_initsafelayout-brilliant-buttons.php:47
filterno_texturize_tagssafelayout-brilliant-buttons.php:48
filterthe_contentsafelayout-brilliant-buttons.php:49
filterwp_enqueue_scriptssafelayout-brilliant-buttons.php:50
filtermce_external_pluginssafelayout-brilliant-buttons.php:51
filtermce_buttonssafelayout-brilliant-buttons.php:52
actionelementor/widgets/registersafelayout-brilliant-buttons.php:54
actionelementor/controls/registersafelayout-brilliant-buttons.php:55
actionelementor/editor/before_enqueue_scriptssafelayout-brilliant-buttons.php:56
actionwp_enqueue_scriptssafelayout-brilliant-buttons.php:57
actionwp_enqueue_scriptssafelayout-brilliant-buttons.php:58
actionelementor/editor/after_enqueue_scriptssafelayout-brilliant-buttons.php:59
actionelementor/editor/footersafelayout-brilliant-buttons.php:60
filterlitespeed_optimize_css_excludessafelayout-brilliant-buttons.php:62
filterlitespeed_optimize_js_excludessafelayout-brilliant-buttons.php:63
filterlitespeed_optm_js_defer_excsafelayout-brilliant-buttons.php:64
filterlitespeed_optm_gm_js_excsafelayout-brilliant-buttons.php:65
filtersgo_js_minify_excludesafelayout-brilliant-buttons.php:66
filtersgo_js_async_excludesafelayout-brilliant-buttons.php:67
filtersgo_javascript_combine_excludesafelayout-brilliant-buttons.php:68
filtersgo_css_combine_excludesafelayout-brilliant-buttons.php:69
filtersgo_css_minify_excludesafelayout-brilliant-buttons.php:70
filterwp-optimize-minify-default-exclusionssafelayout-brilliant-buttons.php:71
filterautoptimize_filter_js_excludesafelayout-brilliant-buttons.php:72
filterautoptimize_filter_css_excludesafelayout-brilliant-buttons.php:73
filterget_rocket_option_remove_unused_css_safelistsafelayout-brilliant-buttons.php:74
filterget_rocket_option_exclude_jssafelayout-brilliant-buttons.php:75
filterget_rocket_option_delay_js_exclusionssafelayout-brilliant-buttons.php:76
filterget_rocket_option_exclude_defer_jssafelayout-brilliant-buttons.php:77
actionadmin_menusafelayout-brilliant-buttons.php:80
actionadmin_initsafelayout-brilliant-buttons.php:81
actionadmin_initsafelayout-brilliant-buttons.php:82
actionadmin_enqueue_scriptssafelayout-brilliant-buttons.php:83
actionadmin_enqueue_scriptssafelayout-brilliant-buttons.php:84
actionadmin_footer-plugins.phpsafelayout-brilliant-buttons.php:85
filterhttp_request_host_is_externalsafelayout-brilliant-buttons.php:87
filterregister_block_type_argssafelayout-brilliant-buttons.php:88
actionadmin_noticessafelayout-brilliant-buttons.php:477
actionadmin_enqueue_scriptssafelayout-brilliant-buttons.php:479
actionadmin_noticessafelayout-brilliant-buttons.php:481
actionadmin_enqueue_scriptssafelayout-brilliant-buttons.php:483
Maintenance & Trust

Safelayout Brilliant Buttons – WordPress Buttons Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 26, 2026
PHP min version7.0
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs50
Developer Profile

Safelayout Brilliant Buttons – WordPress Buttons Developer Profile

safelayout

4 plugins · 11K total installs

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

How We Detect Safelayout Brilliant Buttons – WordPress Buttons

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/safelayout-brilliant-buttons/build/button/style-index.css/wp-content/plugins/safelayout-brilliant-buttons/build/button/script.js
Script Paths
/wp-content/plugins/safelayout-brilliant-buttons/build/button/script.js
Version Parameters
safelayout-brilliant-buttons/build/button/style-index.css?ver=1.2.3safelayout-brilliant-buttons/build/button/script.js?ver=1.2.3

HTML / DOM Fingerprints

CSS Classes
safelayout-safelayout-button-stylesafelayout-safelayout-button-view-script
JS Globals
SAFELAYOUT_BUTTONS_VERSIONSAFELAYOUT_BUTTONS_PATHSAFELAYOUT_BUTTONS_URLSAFELAYOUT_BUTTONS_NAME
FAQ

Frequently Asked Questions about Safelayout Brilliant Buttons – WordPress Buttons