wp-config.php was never hardened and runs default settings
A few lines in wp-config.php close the most-abused attack vectors.
Try this first
- 1Set DISALLOW_FILE_EDIT to true so admins can't edit code via the dashboard
- 2Set WP_DEBUG to false on production, only enable debug logs when troubleshooting
- 3Change the DB table prefix away from 'wp_' on new installs
- 4Restrict wp-config.php permissions to 600 or 640
When to bring us in
Unsure about chmod and ownership, your host support can set correct permissions.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.