Perché un wp-content/debug.log esposto è una falla critica su WordPress
Why debug.log gets left open on production stores
Developers often turn on WP_DEBUG, WP_DEBUG_DISPLAY, and WP_DEBUG_LOG inside wp-config.php while troubleshooting a broken WooCommerce plugin or payment gateway, then forget to switch them back off. Over months, PHP warnings and fatal stack traces accumulate into massive files directly under /wp-content/debug.log.
What attackers extract from a public debug.log
Automated bots routinely probe /wp-content/debug.log across thousands of WordPress domains. Even without direct passwords inside, a debug log reveals exact server filesystem paths, active plugin versions, SQL query fragments, webhook payloads, and occasional API/SMTP error traces that make targeted exploitation trivial.
Check your live setup in 5 seconds without logging in.
How to fix it properly (and why WPRenovator goes further)
Disabling WP_DEBUG in wp-config.php stops new entries, but the existing log file must also be deleted and blocked at the Nginx, Apache, Plesk, or DirectAdmin level. Whether your store runs on Hetzner, IONOS, TransIP, Cloudways, or cPanel, WPRenovator audits your entire surface: closing debug.log, locking /wp-json/wp/v2/users enumeration, disabling XML-RPC, and verifying staging updates.
Frequently asked questions
Can I just delete debug.log via FTP?
Deleting the file removes the immediate leak, but if WP_DEBUG_LOG remains true in wp-config.php, WordPress will recreate it on the next PHP warning.
Does your free scanner check for debug.log safely?
Yes. Our Security Scanner checks whether /wp-content/debug.log returns HTTP 200 without downloading or exposing its contents.
Staging-tested updates, EU/Estonia engineering (Comet Group OÜ), zero-downtime protection from €59/mo.