WP-CDN-Yes – WordPress CDN 插件 Security & Risk Analysis

wordpress.org/plugins/wp-cdn-yes

WordPress CDN 多合一功能插件

10 active installs v2.2.0 PHP 8.0+ WP 5.5+ Updated Oct 1, 2022
cdnchinacontent-delivery-networkcontent-distribution-networkoptimization
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP-CDN-Yes – WordPress CDN 插件 Safe to Use in 2026?

Generally Safe

Score 85/100

WP-CDN-Yes – WordPress CDN 插件 has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 3yr ago
Risk Assessment

The "wp-cdn-yes" plugin v2.2.0 exhibits a strong security posture based on the provided static analysis. The complete absence of identifiable entry points, including AJAX handlers, REST API routes, shortcodes, and cron events, significantly minimizes the attack surface. Furthermore, the code demonstrates excellent security practices by exclusively using prepared statements for SQL queries, having a high percentage of properly escaped outputs, and implementing nonce and capability checks. The lack of identified dangerous functions, file operations, and external HTTP requests further reinforces this positive assessment.

The taint analysis also indicates no critical or high-severity vulnerabilities related to unsanitized data flows, which is a very encouraging sign. The plugin's vulnerability history being completely clean, with no recorded CVEs, suggests a consistent track record of secure development and maintenance. However, the analysis is limited to the provided data, and the absence of certain checks (e.g., 0 AJAX handlers without auth checks) is a reflection of the plugin's minimal entry points rather than a deliberate security feature. The overall assessment is that this plugin appears to be very secure.

Vulnerabilities
None known

WP-CDN-Yes – WordPress CDN 插件 Security Vulnerabilities

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

WP-CDN-Yes – WordPress CDN 插件 Release Timeline

v2.2.0Current
v2.1.0
v2.0.4
v2.0.3
v2.0.2
v2.0.1
Code Analysis
Analyzed Mar 17, 2026

WP-CDN-Yes – WordPress CDN 插件 Code Analysis

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

Output Escaping

94% escaped16 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
multiple_network_options (inc\class-setting.php:594)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP-CDN-Yes – WordPress CDN 插件 Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionplugins_loadedinc\class-plugin.php:16
actionadmin_initinc\class-plugin.php:24
actionadmin_menuinc\class-plugin.php:25
actioninitinc\class-plugin.php:26
filterplugin_action_linksinc\class-plugin.php:82
actionnetwork_admin_edit_wsa-multiple-network-optionsinc\class-setting.php:35
actionadmin_enqueue_scriptsinc\class-setting.php:38
actiontemplate_redirectinc\helper.php:43
Maintenance & Trust

WP-CDN-Yes – WordPress CDN 插件 Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedOct 1, 2022
PHP min version8.0
Downloads8K

Community Trust

Rating100/100
Number of ratings3
Active installs10
Developer Profile

WP-CDN-Yes – WordPress CDN 插件 Developer Profile

耗子

3 plugins · 40 total installs

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

How We Detect WP-CDN-Yes – WordPress CDN 插件

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-cdn-yes/css/setting.css/wp-content/plugins/wp-cdn-yes/js/setting.js
Script Paths
/wp-content/plugins/wp-cdn-yes/js/setting.js

HTML / DOM Fingerprints

JS Globals
wpuf-admin_page
FAQ

Frequently Asked Questions about WP-CDN-Yes – WordPress CDN 插件