Paparan berkas for WordPress
critical5 checks
Repositories, environment files, database dumps and backups are the fastest path from reconnaissance to full compromise.
What WordPress must have
- /.git and /.svn not reachable
- /.env, /.env.local and config backups return 404
- No .sql, .zip or .tar.gz dumps in the web root
- Debug consoles and admin panels not publicly reachable
- Directory listing disabled
How to fix it
- 1Serve nothing from the web root that is not meant to be public
- 2Block dotfiles at the edge and rotate every secret that was exposed
WordPress context
PHP-based CMS powering ~43% of the web, extended through themes and plugins.
Core is rarely the weak point — outdated plugins, xmlrpc.php, user enumeration and exposed debug logs are. Also inherits every PHP runtime CVE.