wp-config.php with DB password ended up in Git.
Removing from history is not enough, the credentials have been public. Rotate everything that was in that file.
Try this first
- 1Change the DB password on the host immediately
- 2Regenerate auth keys and salts in wp-config
- 3Add the file to .gitignore, rewrite history
- 4Review logs for suspicious logins or queries
When to bring us in
Repo was public or a fork exists: assume everything is leaked, also rotate Stripe or mail relay keys.
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.