Send FCM notifications Security & Risk Analysis

wordpress.org/plugins/ss-fcm-notifications

Send notifications to all your Android app user without paying fees as it does not use third-party servers.

100 active installs v1.0 PHP + WP 3.4+ Updated Jan 9, 2018
bulk-messaging-by-google-firebasecustom-firebase-messaginggoogle-firebase-cloud-messagingsend-message-to-all-android-app-user
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Send FCM notifications Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The ss-fcm-notifications plugin v1.0 exhibits a generally strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points significantly limits the plugin's attack surface. Furthermore, the complete absence of dangerous functions, raw SQL queries, and critical or high-severity taint flows is highly positive. The plugin also demonstrates good practice by consistently using prepared statements for all its SQL queries and employing nonce and capability checks where relevant.

However, a notable concern arises from the low percentage (27%) of properly escaped outputs. This indicates a potential risk of cross-site scripting (XSS) vulnerabilities if user-supplied data is not sufficiently sanitized before being displayed to users. While the plugin has no recorded vulnerability history, suggesting a lack of previously exploited weaknesses, the output escaping issue remains a latent risk that could be exploited.

In conclusion, the plugin has several security strengths, particularly in its limited attack surface and secure database interactions. Nevertheless, the insufficient output escaping is a significant weakness that requires attention to mitigate potential XSS risks. The lack of historical vulnerabilities is a positive indicator, but it does not negate the need to address the identified code-level concerns.

Key Concerns

  • Low percentage of properly escaped output
Vulnerabilities
None known

Send FCM notifications Security Vulnerabilities

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

Send FCM notifications Code Analysis

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

Output Escaping

27% escaped11 total outputs
Data Flows
All sanitized

Data Flow Analysis

1 flows
<fcm-settings> (inc\fcm-settings.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Send FCM notifications Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionadmin_menunotifications.php:19
Maintenance & Trust

Send FCM notifications Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedJan 9, 2018
PHP min version
Downloads2K

Community Trust

Rating80/100
Number of ratings1
Active installs100
Developer Profile

Send FCM notifications Developer Profile

dselvainfotech

1 plugin · 100 total installs

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

How We Detect Send FCM notifications

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/ss-fcm-notifications/images/mail-icon.png

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Send FCM notifications