
SmartEmailing Security & Risk Analysis
wordpress.org/plugins/smartemailingSnadný způsob jak propojit svůj web se svým účtem ve SmartEmailingu pro sběr e-mailových adres pomocí webového formuláře.
Is SmartEmailing Safe to Use in 2026?
Generally Safe
Score 91/100SmartEmailing has a strong security track record. Known vulnerabilities have been patched promptly. It's a solid choice for most WordPress installations.
The static analysis of the "smartemailing" plugin v2.2.6 reveals a generally good security posture with no identified critical or high severity vulnerabilities in the code itself. The absence of dangerous functions, raw SQL queries, and external HTTP requests is commendable. While the output escaping is at 84%, which is good, there's a slight concern that 16% of outputs are not properly escaped, potentially leaving room for reflected XSS vulnerabilities if user-controlled data is involved in these specific outputs. The lack of detected taint flows is a positive sign, indicating that the developers have likely implemented proper sanitization for data handling.
The vulnerability history shows one past medium severity CVE, which has since been patched. The common vulnerability type being Cross-site Scripting suggests that developers should maintain vigilance in output escaping. The fact that there are no currently unpatched vulnerabilities is a strong positive indicator. However, the absence of capability checks and nonce checks on entry points is a significant concern. While the attack surface is currently reported as zero, this could be a consequence of the specific analysis performed or a testament to the plugin's limited functionality. If any new entry points are introduced or existing ones are discovered, the lack of these fundamental security controls could lead to serious issues.
In conclusion, the plugin demonstrates strengths in preventing direct code execution and SQL injection. The past vulnerability was addressed, which is positive. However, the reliance on the absence of entry points for security, rather than implementing robust access controls like capability checks and nonce validation, represents a significant weakness. The potential for unescaped output, though not critical, also warrants attention. The plugin is currently in a relatively secure state based on this snapshot, but the lack of foundational access control mechanisms poses a latent risk should the attack surface expand or become more dynamic.
Key Concerns
- No capability checks found
- No nonce checks found
- Unescaped output identified (16%)
- Bundled outdated library (Guzzle)
SmartEmailing Security Vulnerabilities
CVEs by Year
Severity Breakdown
1 total CVE
SmartEmailing.cz <= 2.2.0 - Reflected Cross-Site Scripting
SmartEmailing Release Timeline
SmartEmailing Code Analysis
Bundled Libraries
Output Escaping
SmartEmailing Attack Surface
WordPress Hooks 28
Maintenance & Trust
SmartEmailing Maintenance & Trust
Maintenance Signals
Community Trust
SmartEmailing Alternatives
No alternatives data available yet.
SmartEmailing Developer Profile
1 plugin · 600 total installs
How We Detect SmartEmailing
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/smartemailing/smartemailing.phphttps://app.smartemailing.cz/js/tracking/tracker.jsHTML / DOM Fingerprints
smartemailing_se