Home Security Knowledge Base CMS & Web Frameworks wp-content/debug.log

Security Knowledge Base

Comprehensive documentation for security researchers and professionals

wp-content/debug.log

Security Researcher Detected: You might have ended up here because your site vulnerability scanner found something interesting. Hi! I'm a security engineer and I'm having a good time interacting with the people and bots that are interested in information security.

You will hopefully find this site is well-secured and I'm not interested in being hacked. I'm interested in learning about how people try to hack me, though.

What is this endpoint?

wp-content/debug.log

WordPress debug log that can leak paths, queries, and errors when WP_DEBUG_LOG is enabled

What an attacker could do

If readable, this file leaks absolute server paths, database queries, plugin errors, and occasionally credentials or tokens, providing reconnaissance to chain further exploits.

How to defend it

Disable `WP_DEBUG_LOG` in production, write debug logs outside the web root, and deny direct HTTP access to `.log` files in the server configuration.

Connect with the Security Engineer

Follow me on these platforms where I occasionally share interesting security insights and research.

Learn More

Want to dive deeper into this topic? Check out the official documentation.

Read Official Documentation