ScreenCloud Security & Risk Analysis

wordpress.org/plugins/screencloud

Push content from WordPress to your screens seamlessly with ScreenCloud, auto-transforming data into designs for digital signage.

30 active installs v1.0.1 PHP 7.2+ WP 5.2+ Updated Jan 13, 2025
communicationdeskless-workersdigital-signageemployee-engagementscreen-content
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is ScreenCloud Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The screencloud plugin version 1.0.1 exhibits a strong security posture based on the provided static analysis and vulnerability history. The code demonstrates excellent adherence to security best practices, with all identified AJAX handlers and other entry points properly secured by authentication and capability checks. The absence of dangerous functions, raw SQL queries, unescaped output, and file operations further bolsters its safety. The plugin's single external HTTP request is a minor point of potential concern, but without further context, its risk is low. The lack of any recorded vulnerabilities, CVEs, or taint flows with unsanitized paths indicates a mature and well-maintained codebase.

While the plugin's current security is impressive, it's important to acknowledge that security is an ongoing process. The low version number and absence of a vulnerability history could also suggest limited exposure or a very new plugin, rather than absolute immunity. However, based on the available data, the plugin appears to be robust and has been developed with security in mind, presenting a very low-risk profile for users.

Key Concerns

  • External HTTP requests detected
Vulnerabilities
None known

ScreenCloud Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

ScreenCloud Release Timeline

v1.0.1Current
v1.0.0
Code Analysis
Analyzed Mar 16, 2026

ScreenCloud Code Analysis

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

Output Escaping

100% escaped39 total outputs
Attack Surface

ScreenCloud Attack Surface

Entry Points2
Unprotected0

AJAX Handlers 2

authwp_ajax_screencloud_send_postincludes\ajax-handlers.php:168
noprivwp_ajax_screencloud_send_postincludes\ajax-handlers.php:169
WordPress Hooks 6
actionadmin_noticesincludes\activation.php:41
actionadmin_menuincludes\admin-settings.php:13
actionadmin_initincludes\admin-settings.php:43
actionadmin_enqueue_scriptsincludes\enqueue-scripts.php:44
filterpost_row_actionsincludes\post-sharing.php:16
actionadmin_footerincludes\post-sharing.php:48
Maintenance & Trust

ScreenCloud Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedJan 13, 2025
PHP min version7.2
Downloads909

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

ScreenCloud Developer Profile

screencloud

1 plugin · 30 total installs

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

How We Detect ScreenCloud

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/screencloud/css/screencloud.css/wp-content/plugins/screencloud/js/screencloud-settings.js/wp-content/plugins/screencloud/js/screencloud-modal.js
Script Paths
screencloud-settings-jsscreencloud-modal-js
Version Parameters
screencloud/css/screencloud.css?ver=screencloud/js/screencloud-settings.js?ver=screencloud/js/screencloud-modal.js?ver=

HTML / DOM Fingerprints

JS Globals
screencloudAjax
REST Endpoints
/wp-json/
FAQ

Frequently Asked Questions about ScreenCloud