Waves Block Security & Risk Analysis

wordpress.org/plugins/waves

Gradients in motion.

800 active installs v1.0.2 PHP + WP 5.4+ Updated May 25, 2022
blockblockswaves
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Waves Block Safe to Use in 2026?

Generally Safe

Score 85/100

Waves Block has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 3yr ago
Risk Assessment

Based on the static analysis and vulnerability history provided, the 'waves' plugin version 1.0.2 exhibits an exceptionally strong security posture. The static analysis reveals zero identified attack vectors, including AJAX handlers, REST API routes, shortcodes, and cron events. Furthermore, there are no detected dangerous functions, file operations, or external HTTP requests. The code demonstrates excellent practices with 100% of SQL queries using prepared statements and 100% of outputs being properly escaped, with zero taint analysis issues flagged.

The complete absence of known CVEs and a clean vulnerability history, with no recorded vulnerabilities of any severity, reinforces this positive assessment. This pattern suggests a plugin that has either been exceptionally well-developed with security as a primary concern from the outset, or one that has undergone rigorous security auditing and remediation. The plugin also reports no bundled libraries, which removes the risk associated with outdated or vulnerable third-party code.

In conclusion, the 'waves' plugin v1.0.2 appears to be highly secure, with no evidence of exploitable vulnerabilities or common security weaknesses found in the provided data. Its robust handling of potential attack vectors and adherence to secure coding practices are commendable strengths. The absence of any security concerns across multiple analysis dimensions points to a well-maintained and secure plugin.

Vulnerabilities
None known

Waves Block Security Vulnerabilities

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

Waves Block Code Analysis

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

Waves Block Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitblocks\waves.php:3
actionenqueue_block_editor_assetsblocks\waves.php:29
actioninitindex.php:13
Maintenance & Trust

Waves Block Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedMay 25, 2022
PHP min version
Downloads5K

Community Trust

Rating86/100
Number of ratings3
Active installs800
Developer Profile

Waves Block Developer Profile

Automattic

213 plugins · 19.2M total installs

73
trust score
Avg Security Score
92/100
Avg Patch Time
1384 days
View full developer profile
Detection Fingerprints

How We Detect Waves Block

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/waves/index.js/wp-content/plugins/waves/style.css/wp-content/plugins/waves/editor.css/wp-content/plugins/waves/twgl/twgl.js/wp-content/plugins/waves/waves.js
Script Paths
index.jstwgl/twgl.jswaves.js
Version Parameters
a8c-wavesa8c-waves-editora8c-waves-js

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Waves Block