E-carousel Security & Risk Analysis

wordpress.org/plugins/e-carousel

E-carousel by http://www.webegenius.es/

10 active installs v1.1 PHP + WP 3.0.1+ Updated Unknown
carouselcarousel-sliderjquery-carouselpost-bannerpost-slider
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is E-carousel Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

Based on the provided static analysis and vulnerability history, the e-carousel plugin version 1.1 exhibits a strong security posture. The plugin has no recorded vulnerabilities, which is a significant positive indicator. Furthermore, the static analysis reveals a clean codebase with no dangerous functions, no raw SQL queries, and all output properly escaped. The absence of file operations and external HTTP requests also reduces potential attack vectors. The plugin appears to implement capability checks for its entry points, which is a good practice for ensuring authorized access.

However, there are a few areas that, while not indicating immediate critical risks based on this data, warrant careful consideration. The most notable absence is the lack of nonce checks on any of its entry points, including the single shortcode. While capability checks are present, nonce checks are a crucial layer of defense against Cross-Site Request Forgery (CSRF) attacks. The fact that taint analysis showed zero flows is excellent, but the analysis itself was limited to zero flows, which might suggest the analysis depth was insufficient for this plugin, or that the plugin truly has no such exploitable patterns. Therefore, while the plugin seems secure currently, the omission of nonce checks represents a potential weakness that could be exploited if other security measures fail or are circumvented.

Key Concerns

  • Missing nonce checks on entry points
Vulnerabilities
None known

E-carousel Security Vulnerabilities

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

E-carousel Code Analysis

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

E-carousel Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[e_carousel] includes\efunctions.php:29
WordPress Hooks 4
filtermce_external_pluginse_carousel.php:38
filtermce_buttonse_carousel.php:39
actionadmin_heade_carousel.php:42
actioninite_carousel.php:117
Maintenance & Trust

E-carousel Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

E-carousel Developer Profile

Web

2 plugins · 20 total installs

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

How We Detect E-carousel

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/e-carousel/assets/js/eslick.min.js/wp-content/plugins/e-carousel/assets/js/emain.js/wp-content/plugins/e-carousel/assets/css/font-awesome.min.css/wp-content/plugins/e-carousel/assets/css/eslick.css/wp-content/plugins/e-carousel/assets/js/e-button.js
Script Paths
assets/js/eslick.min.jsassets/js/emain.jsassets/js/e-button.js

HTML / DOM Fingerprints

CSS Classes
e-carousel
Shortcode Output
<div class="e-carousel autoplay"><div class="image">
FAQ

Frequently Asked Questions about E-carousel