WHMCS Multi-Site Provisioning Security & Risk Analysis

wordpress.org/plugins/remote-provisioning

This plugin allows provisioning of blogs on a Wordpress multi-site installation from external packages and billing systems such as WHMCS.

10 active installs v1.7.0 PHP + WP + Updated Sep 28, 2020
billinghostingintegrationsupportwhmcs
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WHMCS Multi-Site Provisioning Safe to Use in 2026?

Generally Safe

Score 85/100

WHMCS Multi-Site Provisioning 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

The remote-provisioning plugin v1.7.0 exhibits a mixed security posture. On the positive side, it demonstrates good practices by avoiding known dangerous functions and executing all SQL queries using prepared statements, which significantly mitigates SQL injection risks. The plugin also has no recorded vulnerability history, suggesting a low tendency for public exploits. However, several concerning areas are identified. The low percentage of properly escaped output (25%) indicates a high likelihood of Cross-Site Scripting (XSS) vulnerabilities, especially since there are 8 outputs in total. Furthermore, the taint analysis reveals 2 flows with unsanitized paths, which could potentially lead to local file inclusion or other path traversal vulnerabilities if not handled carefully, even though they are not classified as critical or high severity in this analysis. The absence of nonce and capability checks on potential entry points (though the attack surface appears minimal in this specific analysis) is a general concern that can be exploited if new entry points are introduced or if existing ones are indirectly exposed. The plugin's strengths lie in its clean SQL handling and lack of historical vulnerabilities. Its weaknesses stem from output escaping issues and the presence of unsanitized paths in taint flows, demanding careful review.

Key Concerns

  • Low percentage of properly escaped output
  • Flows with unsanitized paths found
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

WHMCS Multi-Site Provisioning Security Vulnerabilities

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

WHMCS Multi-Site Provisioning Code Analysis

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

Output Escaping

25% escaped8 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
cc_rp_admin (rp.php:284)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WHMCS Multi-Site Provisioning Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_noticesrp.php:27
actioninitrp.php:28
actionadmin_menurp.php:337
Maintenance & Trust

WHMCS Multi-Site Provisioning Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedSep 28, 2020
PHP min version
Downloads10K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

WHMCS Multi-Site Provisioning Developer Profile

Global Programming

2 plugins · 4K total installs

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

How We Detect WHMCS Multi-Site Provisioning

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/remote-provisioning/css/style.css/wp-content/plugins/remote-provisioning/js/remote-provisioning.js
Script Paths
/wp-content/plugins/remote-provisioning/js/remote-provisioning.js
Version Parameters
remote-provisioning/css/style.css?ver=remote-provisioning/js/remote-provisioning.js?ver=

HTML / DOM Fingerprints

JS Globals
window.cc_rp
FAQ

Frequently Asked Questions about WHMCS Multi-Site Provisioning