WooSite Security & Risk Analysis

wordpress.org/plugins/woosite

WooSite is used to connect to the WooMulti plugin, as such it requires the WooMulti plugin on your main site.

10 active installs v1.7 PHP 5.6+ WP 4.6+ Updated Jan 23, 2019
multi-storemulti-siteorderswoocommercewoomulti
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WooSite Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The 'woosite' plugin v1.7 exhibits a concerning security posture primarily due to a significant lack of input validation and authorization checks, despite a clean vulnerability history. The static analysis reveals two REST API routes that are entirely unprotected, representing direct entry points for potential attackers. Furthermore, all six identified output operations are not properly escaped, creating a high risk of Cross-Site Scripting (XSS) vulnerabilities where user-supplied data could be injected and executed in the browser. While the plugin demonstrates good practices by avoiding dangerous functions, raw SQL queries, file operations, and external HTTP requests, the absence of nonces and capability checks on entry points is a critical oversight. The lack of any recorded vulnerabilities in its history could indicate a lack of rigorous security auditing or that vulnerabilities have simply not been discovered or publicly disclosed. The plugin's strengths lie in its clean code regarding SQL and avoidance of risky functions, but these are heavily overshadowed by the critical unescapable outputs and unprotected API routes, making it a potentially vulnerable target.

Key Concerns

  • REST API routes without permission callbacks
  • Output escaping: 0% properly escaped
  • Nonce checks: 0
  • Capability checks: 0
Vulnerabilities
None known

WooSite Security Vulnerabilities

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

WooSite Release Timeline

v1.7Current
v1.6
Code Analysis
Analyzed Mar 17, 2026

WooSite Code Analysis

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

Output Escaping

0% escaped6 total outputs
Attack Surface
2 unprotected

WooSite Attack Surface

Entry Points2
Unprotected2

REST API Routes 2

POST/wp-json/gbwm/v1/UpdateBillingAddressgenbuz-woosite.php:50
POST/wp-json/gbwm/v1/UpdateShippingAddressgenbuz-woosite.php:55
WordPress Hooks 3
actionrest_api_initgenbuz-woosite.php:28
actionwoocommerce_order_details_after_order_tablegenbuz-woosite.php:34
actionwoocommerce_email_after_order_tablegenbuz-woosite.php:40
Maintenance & Trust

WooSite Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedJan 23, 2019
PHP min version5.6
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WooSite Developer Profile

GenBuz

1 plugin · 10 total installs

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

How We Detect WooSite

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
woocommerce-table__tracking-numberwoocommerce-table__tracking-url
Data Attributes
width="50%"
REST Endpoints
/gbwm/v1/UpdateBillingAddress/gbwm/v1/UpdateShippingAddress
FAQ

Frequently Asked Questions about WooSite