Wavatars Security & Risk Analysis

wordpress.org/plugins/wavatars

Wavatars will generate and assign icons to the visitors leaving comments at your site. It can optionally show Gravatars as well.

10 active installs v1.1.3 PHP + WP 2.0.2+ Updated Mar 25, 2008
avatarscommentsgravtarsicons
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Wavatars Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 18yr ago
Risk Assessment

The wavatars plugin v1.1.3 exhibits a generally strong security posture regarding known external threats and common WordPress vulnerabilities. The absence of any recorded CVEs and the plugin's adherence to using prepared statements for SQL queries are positive indicators. Furthermore, the static analysis reveals no direct attack surface through AJAX, REST API, shortcodes, or cron events that are not protected by authentication or permission checks, and no dangerous functions are utilized. However, there are notable areas for improvement. The low percentage of properly escaped output (13%) presents a significant risk of Cross-Site Scripting (XSS) vulnerabilities, as user-supplied data may be rendered without sufficient sanitization. Additionally, the taint analysis shows flows with unsanitized paths, which, while not classified as critical or high severity in this instance, still warrant careful review to prevent potential path traversal or file manipulation issues. The presence of file operations without further context also raises a mild concern. Overall, while the plugin appears to avoid common pitfalls and has a clean vulnerability history, the lack of robust output escaping and the presence of unsanitized path flows are weaknesses that could be exploited.

Key Concerns

  • Low percentage of properly escaped output
  • Flows with unsanitized paths found
  • File operations present
Vulnerabilities
None known

Wavatars Security Vulnerabilities

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

Wavatars Code Analysis

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

Output Escaping

13% escaped16 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
wavatar_options (wavatars.php:51)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Wavatars Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menuwavatars.php:443
filterget_comment_authorwavatars.php:444
actionwp_footerwavatars.php:445
Maintenance & Trust

Wavatars Maintenance & Trust

Maintenance Signals

WordPress version tested2.3.1
Last updatedMar 25, 2008
PHP min version
Downloads11K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Wavatars Developer Profile

shamusyoung

1 plugin · 10 total installs

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

How We Detect Wavatars

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wavatars/wavatar.js/wp-content/plugins/wavatars/wavatar.css
Script Paths
/wp-content/plugins/wavatars/wavatar.js
Version Parameters
wavatars/wavatar.js?ver=wavatars/wavatar.css?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- This is used to help build the options page. --><!-- This builds the options page where you can administrate the plugin rather than mucking about here in the source code. Which you seem to be doing anyway. -->
Data Attributes
name="wavatar_update"name="wavatar_clear_cache"id="wavatar_auto"id="wavatar_size"id="wavatar_border"id="wavatar_suffix"+5 more
FAQ

Frequently Asked Questions about Wavatars