Ewebdevs Elements Security & Risk Analysis

wordpress.org/plugins/ewebdevs-elements

Ewebdevs Elements.

0 active installs v1.0.0 PHP + WP 5.0+ Updated Mar 19, 2021
elementorelementor-addonselementor-extentionelementor-testimonial-sectionelementor-widget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Ewebdevs Elements Safe to Use in 2026?

Generally Safe

Score 85/100

Ewebdevs Elements 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 static analysis and vulnerability history, the ewebdevs-elements plugin version 1.0.0 exhibits an exceptionally strong security posture. The absence of any detected attack surface entry points, dangerous functions, or taint flows suggests a highly secure codebase. Furthermore, the plugin demonstrates excellent data handling practices with 100% of SQL queries using prepared statements and a very high percentage (95%) of output properly escaped. The complete lack of any known CVEs further reinforces its current security integrity.

While the current analysis shows no immediate risks, it is important to acknowledge that static analysis and historical data have limitations. The complete absence of detectable entry points (AJAX, REST API, shortcodes, cron events) is a significant strength, but it also means there are no immediately verifiable security controls like nonce or capability checks to assess in this version. The plugin's current security is excellent, but a lack of publicly documented security events or checks means there's no historical data to predict future behavior under attack or evolution.

In conclusion, ewebdevs-elements v1.0.0 appears to be a highly secure plugin based on the provided data. Its robust coding practices and clean vulnerability history are commendable. However, the complete lack of discoverable entry points or common security checks makes a direct assessment of those specific controls impossible from this data alone. Future updates should be monitored for the introduction of new features that might expose new attack vectors.

Vulnerabilities
None known

Ewebdevs Elements Security Vulnerabilities

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

Ewebdevs Elements Code Analysis

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

Output Escaping

95% escaped19 total outputs
Attack Surface

Ewebdevs Elements Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
actioninitewebdevs-elements.php:61
actionplugins_loadedewebdevs-elements.php:64
actionadmin_noticesewebdevs-elements.php:97
actionadmin_noticesewebdevs-elements.php:103
actionadmin_noticesewebdevs-elements.php:109
actionelementor/frontend/after_enqueue_stylesewebdevs-elements.php:113
actionelementor/frontend/after_enqueue_scriptsewebdevs-elements.php:114
actionelementor/widgets/widgets_registeredplugin.php:104
actionelementor/elements/categories_registeredplugin.php:107
Maintenance & Trust

Ewebdevs Elements Maintenance & Trust

Maintenance Signals

WordPress version tested5.6.17
Last updatedMar 19, 2021
PHP min version
Downloads949

Community Trust

Rating100/100
Number of ratings1
Active installs0
Developer Profile

Ewebdevs Elements Developer Profile

naimkst

1 plugin · 0 total installs

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

How We Detect Ewebdevs Elements

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/ewebdevs-elements/assets/js/popper.js/wp-content/plugins/ewebdevs-elements/assets/js/min.min.js/wp-content/plugins/ewebdevs-elements/assets/js/placeholdem.min.js/wp-content/plugins/ewebdevs-elements/assets/js/lib/slick/slick.js/wp-content/plugins/ewebdevs-elements/assets/js/script.js/wp-content/plugins/ewebdevs-elements/assets/css/animate.css/wp-content/plugins/ewebdevs-elements/assets/css/bootstrap.min.css/wp-content/plugins/ewebdevs-elements/assets/css/all.min.css+5 more
Script Paths
/wp-content/plugins/ewebdevs-elements/assets/js/popper.js/wp-content/plugins/ewebdevs-elements/assets/js/min.min.js/wp-content/plugins/ewebdevs-elements/assets/js/placeholdem.min.js/wp-content/plugins/ewebdevs-elements/assets/js/lib/slick/slick.js/wp-content/plugins/ewebdevs-elements/assets/js/script.js
Version Parameters
ewebdevs-elements/assets/js/popper.js?ver=ewebdevs-elements/assets/js/min.min.js?ver=ewebdevs-elements/assets/js/placeholdem.min.js?ver=ewebdevs-elements/assets/js/lib/slick/slick.js?ver=ewebdevs-elements/assets/js/script.js?ver=ewebdevs-elements/assets/css/animate.css?ver=ewebdevs-elements/assets/css/bootstrap.min.css?ver=ewebdevs-elements/assets/css/all.min.css?ver=ewebdevs-elements/assets/css/flaticon.css?ver=ewebdevs-elements/assets/js/lib/slick/slick.css?ver=ewebdevs-elements/assets/js/lib/slick/slick-theme.css?ver=ewebdevs-elements/assets/css/style.css?ver=ewebdevs-elements/assets/css/responsive.css?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- Ewebdevs Elements -->
FAQ

Frequently Asked Questions about Ewebdevs Elements