SECURITY4 min read
When WP_DEBUG_LOG is enabled in production without Nginx/Apache restrictions, anyone can download /wp-content/debug.log (often 50-200 MB of stack traces, server paths, and plugin errors). Run an external check immediately and disable public debug logging.
VULNERABILITIES5 min read
Automated scanners begin probing newly disclosed WordPress plugin vulnerabilities within a median of 5 hours. Waiting for monthly manual updates leaves live stores wide open, while blind auto-updates risk breaking WooCommerce checkout.
PERFORMANCE5 min read
High Time to First Byte (TTFB) on WooCommerce usually comes from uncached anonymous requests, unindexed wp_postmeta or security plugin log tables growing over 100 MB, and missing Brotli/Gzip compression.
HARDENING4 min read
Default WordPress and European shared hosting setups (DirectAdmin, Plesk, cPanel) omit HSTS, CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy, leaving admin and checkout pages exposed to clickjacking and downgrade attacks.
INCIDENT RESPONSE6 min read
Simply deleting infected files or restoring a recent backup rarely stops reinfection if the original vulnerable plugin, rogue admin account, or database injection remains. Full cleanup requires core checksum verification, DB inspection, credential rotation, and patching.