PURGE BOX Security & Risk Analysis

wordpress.org/plugins/purgebox

合同会社レッドボックスが提供している「定額CDN エッジキャッシュCDN」全サービスでご利用できるWordpress用キャッシュ削除プラグインです。

10 active installs v1.9 PHP + WP 4.6+ Updated Dec 22, 2024
cache-deletecdnpurgeredbox
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is PURGE BOX Safe to Use in 2026?

Generally Safe

Score 92/100

PURGE BOX 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 Purgebox plugin v1.9 exhibits a strong security posture based on the provided static analysis. It has zero reported CVEs, indicating a clean history. The code signals show excellent adherence to secure coding practices, with all SQL queries utilizing prepared statements and a high percentage of output being properly escaped. Furthermore, the absence of dangerous functions, file operations, and external HTTP requests reduces the potential attack surface. The plugin also implements nonce and capability checks where relevant.

While the attack surface appears to be zero, which is ideal, the single external HTTP request warrants a minor note. Although the taint analysis shows no critical or high severity flows, this external communication could theoretically be a vector if not handled with extreme care in its implementation. The lack of historical vulnerabilities is a significant strength, suggesting good development practices and diligent maintenance. Overall, Purgebox v1.9 appears to be a secure plugin, with its primary strength being the lack of known vulnerabilities and its adherence to secure coding principles, with only a minor point of attention being the single external HTTP request.

Key Concerns

  • External HTTP request detected
Vulnerabilities
None known

PURGE BOX Security Vulnerabilities

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

PURGE BOX Release Timeline

v1.6
v1.5
Code Analysis
Analyzed Apr 16, 2026

PURGE BOX Code Analysis

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

Output Escaping

92% escaped13 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
purgebox_render_network_settings_page (purgebox.php:105)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

PURGE BOX Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actiontransition_post_statusclasses/class-purgebox-purge.php:36
actiondelete_postclasses/class-purgebox-purge.php:37
actionedit_categoryclasses/class-purgebox-purge.php:39
actionedit_link_categoryclasses/class-purgebox-purge.php:40
actionedit_post_tagclasses/class-purgebox-purge.php:41
actionplugins_loadedpurgebox.php:64
actionnetwork_admin_menupurgebox.php:95
Maintenance & Trust

PURGE BOX Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedDec 22, 2024
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

PURGE BOX Developer Profile

katsuhisa ogawa

1 plugin · 10 total installs

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

How We Detect PURGE BOX

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

Asset Fingerprints

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

HTML / DOM Fingerprints

CSS Classes
purgebox-purge-path-settings
Data Attributes
data-purgebox-url
JS Globals
PurgeBox
FAQ

Frequently Asked Questions about PURGE BOX