Say hello Security & Risk Analysis

wordpress.org/plugins/greeting-by-day-time

Greet your website visitors by time of day with shortcode on pages or posts.

100 active installs v1.0 PHP 8.0+ WP 6.9+ Updated Jan 9, 2026
greet-your-website-visitors-by-time-of-day
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Say hello Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 2mo ago
Risk Assessment

The "greeting-by-day-time" plugin v1.0 exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, SQL queries, file operations, and external HTTP requests is a significant positive. Furthermore, all SQL queries use prepared statements, and all output is properly escaped, mitigating common risks like SQL injection and Cross-Site Scripting (XSS).

However, the analysis does reveal a notable concern: the complete lack of nonce checks and capability checks across all identified entry points (10 shortcodes). While there are no AJAX handlers or REST API routes to directly exploit in this specific version, the presence of shortcodes as entry points without any authorization checks creates a significant potential vulnerability. If any of these shortcodes were to process user-supplied data or have any administrative functionality, it could be exploited without authentication or proper authorization.

The plugin's vulnerability history is clean, with no recorded CVEs. This, combined with the absence of critical taint flows and dangerous functions in the code analysis, suggests that the developers have a good understanding of secure coding practices. Nevertheless, the identified lack of authorization checks on shortcodes is a critical weakness that needs to be addressed to ensure comprehensive security.

Key Concerns

  • Missing nonce checks on shortcodes
  • Missing capability checks on shortcodes
Vulnerabilities
None known

Say hello Security Vulnerabilities

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

Say hello Code Analysis

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

Output Escaping

100% escaped22 total outputs
Attack Surface

Say hello Attack Surface

Entry Points10
Unprotected0

Shortcodes 10

[dorud_irn] SayHello.php:50
[hello_en] SayHello.php:70
[heileo_ir] SayHello.php:89
[bonjour_fr] SayHello.php:108
[hola_sp] SayHello.php:127
[ciao_it] SayHello.php:149
[nihao_chn] SayHello.php:171
[chairete_grc] SayHello.php:192
[czesc_pol] SayHello.php:216
[mrhban_ae] SayHello.php:238
Maintenance & Trust

Say hello Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedJan 9, 2026
PHP min version8.0
Downloads1K

Community Trust

Rating100/100
Number of ratings2
Active installs100
Developer Profile

Say hello Developer Profile

Benjamin Hagh Parast

18 plugins · 330 total installs

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

How We Detect Say hello

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
Guten MorgenGuten TagGuten Abendصبح به خیر
FAQ

Frequently Asked Questions about Say hello