Bomb – SMS Notifier Security & Risk Analysis

wordpress.org/plugins/bomb-sms-notifier

WooCommerce order sms, order notification, custom order sms, send quick sms.

0 active installs v1.0.0 PHP + WP 4.7+ Updated Oct 29, 2020
messagenotificationquick-smssmswoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Bomb – SMS Notifier Safe to Use in 2026?

Generally Safe

Score 85/100

Bomb – SMS Notifier has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5yr ago
Risk Assessment

Based on the provided static analysis, the "bomb-sms-notifier" plugin v1.0.0 exhibits a generally good security posture. There are no identified dangerous functions, SQL queries are all prepared, and the majority of output is properly escaped. The plugin also correctly implements nonce and capability checks, indicating an awareness of core WordPress security practices. The absence of any recorded vulnerabilities, CVEs, or concerning taint flows further strengthens this assessment.

However, it's important to note the complete lack of identified entry points (AJAX handlers, REST API routes, shortcodes, cron events) in the static analysis. While this suggests a minimal attack surface, it could also indicate limitations in the static analysis tool itself or that the plugin's functionality is entirely passive and relies on external triggers. The bundled Guzzle library, while not explicitly flagged as a vulnerability here, should be monitored for potential security issues in its own right, especially if it's an older version.

In conclusion, "bomb-sms-notifier" v1.0.0 appears to be a secure plugin based on the current data, with strong adherence to fundamental WordPress security best practices. The lack of historical vulnerabilities is a positive indicator. The only minor points of consideration are the potential for the static analysis to be incomplete in identifying entry points and the general need to keep bundled libraries updated.

Key Concerns

  • Bundled Guzzle library detected
Vulnerabilities
None known

Bomb – SMS Notifier Security Vulnerabilities

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

Bomb – SMS Notifier Code Analysis

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

Bundled Libraries

Guzzle

Output Escaping

86% escaped43 total outputs
Attack Surface

Bomb – SMS Notifier Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
filtersms_notifier_providersAdmin\Providers.php:12
actionadmin_enqueue_scriptsAdmin\Settings.php:11
actionadmin_menuAdmin\Settings.php:12
actioninitAdmin\SmsGatewayInit.php:24
actionadmin_initbomb.php:53
actionplugins_loadedbomb.php:59
actionadmin_noticesbomb.php:130
Maintenance & Trust

Bomb – SMS Notifier Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedOct 29, 2020
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Bomb – SMS Notifier Developer Profile

redq

5 plugins · 300 total installs

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

How We Detect Bomb – SMS Notifier

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bomb-sms-notifier/assets/css/sms-notifier.css/wp-content/plugins/bomb-sms-notifier/assets/js/sms-notifier.js
Script Paths
/wp-content/plugins/bomb-sms-notifier/assets/js/sms-notifier.js
Version Parameters
bomb-sms-notifier/assets/css/sms-notifier.css?ver=bomb-sms-notifier/assets/js/sms-notifier.js?ver=

HTML / DOM Fingerprints

JS Globals
SMS_NOTIFIER_DATA
FAQ

Frequently Asked Questions about Bomb – SMS Notifier