CC-Deploy Security & Risk Analysis

wordpress.org/plugins/cc-deploy

This plugin allows you to deploy your WordPress site source code from git repository using webhooks.

0 active installs v1.0.1 PHP + WP 4.8.2+ Updated Mar 13, 2018
deploydeploymentgitgithubrepository
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is CC-Deploy Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The 'cc-deploy' v1.0.1 plugin exhibits a generally good security posture in terms of its attack surface and known vulnerabilities. There are no recorded CVEs or common vulnerability types, suggesting a history of stable and secure development. The plugin also demonstrates strong practices in its database interactions, with all SQL queries utilizing prepared statements. Furthermore, the absence of file operations, external HTTP requests, and bundled libraries are positive indicators.

However, the static analysis reveals significant concerns. The presence of the `shell_exec` function is a critical risk, as it can be exploited to execute arbitrary operating system commands if not properly secured. The extremely low percentage of properly escaped output (7%) indicates a high likelihood of cross-site scripting (XSS) vulnerabilities. The complete lack of nonce and capability checks across all identified entry points (though currently zero) is a major weakness that would be catastrophic if any entry points were to be introduced or if the count increases without addressing this.

In conclusion, while the plugin has a clean vulnerability history and good database practices, the critical `shell_exec` function and widespread output escaping deficiencies present substantial security risks. The absence of authentication and authorization checks on potential entry points is a fundamental security flaw that needs immediate attention.

Key Concerns

  • Dangerous function shell_exec detected
  • Low output escaping percentage (7%)
  • 0 Nonce checks for entry points
  • 0 Capability checks for entry points
Vulnerabilities
None known

CC-Deploy Security Vulnerabilities

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

CC-Deploy Release Timeline

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

CC-Deploy Code Analysis

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

Dangerous Functions Found

shell_exec$log = shell_exec( $settings->git . ' pull 2>&1' );includes/rest.php:74
shell_execDeploy::get_template( 'code', [ 'content' => shell_exec( $git . ' pull 2>&1' ) ] ) ),includes/settings.php:382

SQL Query Safety

100% prepared3 total queries

Output Escaping

7% escaped29 total outputs
Attack Surface

CC-Deploy Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

CC-Deploy Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedMar 13, 2018
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

CC-Deploy Developer Profile

Clearcode

19 plugins · 220 total installs

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

How We Detect CC-Deploy

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

Asset Fingerprints

Script Paths
/wp-content/plugins/cc-deploy/assets/js/cc-deploy.js
Version Parameters
cc-deploy/assets/js/cc-deploy.js?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- CC-Deploy --><!-- CC-Deploy: Token -->
Data Attributes
data-nonce
JS Globals
ccDeploySettings
REST Endpoints
/wp-json/cc-deploy/v1/webhook
Shortcode Output
<a href="https://wordpress.org/plugins/cc-deploy" target="_blank">CC-Deploy</a><span class="cc-deploy-code"></span>
FAQ

Frequently Asked Questions about CC-Deploy