WP PLC Connect Security & Risk Analysis

wordpress.org/plugins/wp-plc-connect

A simple plugin to work with onePlace. Needed for all other onePlace Wordpress Plugins.

0 active installs v1.0.3 PHP 5.4+ WP 4.6+ Updated Mar 11, 2020
apioneplace
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP PLC Connect Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The wp-plc-connect plugin version 1.0.3 exhibits a generally positive security posture based on the static analysis and vulnerability history. The absence of known CVEs, critical taint flows, and dangerous functions is a strong indicator of good development practices. Furthermore, the plugin demonstrates good handling of SQL queries by exclusively using prepared statements. However, a significant area of concern is the low percentage of properly escaped output, with only 4% of 24 outputs being escaped. This could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is displayed without adequate sanitization. The presence of external HTTP requests, while not inherently a vulnerability, warrants careful monitoring for potential supply chain or SSRF risks in future analyses.

Despite the lack of critical findings in taint analysis and the absence of historical vulnerabilities, the insufficient output escaping presents a tangible risk. While the attack surface is small and appears to be protected by some form of checks, the unescaped output could still be exploited. The plugin's strengths lie in its SQL handling and lack of known vulnerabilities, but the output escaping deficiency is a notable weakness that needs to be addressed to improve its overall security.

Key Concerns

  • Low percentage of properly escaped output
  • External HTTP requests present
Vulnerabilities
None known

WP PLC Connect Security Vulnerabilities

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

WP PLC Connect Code Analysis

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

Output Escaping

4% escaped24 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
updateSettings (includes\Modules\Settings.php:141)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP PLC Connect Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_save_plcsettingsincludes\Modules\Settings.php:44
WordPress Hooks 4
actionadmin_enqueue_scriptsincludes\Modules\Settings.php:32
actionadmin_menuincludes\Modules\Settings.php:35
actionadmin_initincludes\Modules\Settings.php:38
actionplugins_loadedincludes\Modules\Settings.php:41
Maintenance & Trust

WP PLC Connect Maintenance & Trust

Maintenance Signals

WordPress version tested5.4.19
Last updatedMar 11, 2020
PHP min version5.4
Downloads967

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

WP PLC Connect Developer Profile

onePlace

2 plugins · 10 total installs

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

How We Detect WP PLC Connect

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-plc-connect/assets/css/plc-admin-style.css/wp-content/plugins/wp-plc-connect/assets/js/plc-admin.js
Script Paths
/wp-content/plugins/wp-plc-connect/assets/js/plc-admin.js
Version Parameters
wp-plc-connect/assets/css/plc-admin-style.css?ver=wp-plc-connect/assets/js/plc-admin.js?ver=

HTML / DOM Fingerprints

JS Globals
plcAdminControls
FAQ

Frequently Asked Questions about WP PLC Connect