Every check / config-backup-exposed
Is a backup of your configuration file showing your database password?
On a domain you have proved is yours, we ask for /wp-config.php.bak and /config.php.bak, the copies people leave when they edit a file in place.
How it decides
The check speaks up only when what comes back contains database settings such as DB_PASSWORD.
Why it matters
The live configuration file is run by the server, so nobody sees inside it.
In more detail
A backup with a different ending is handed over as plain text instead, database username and password included. The file needs deleting and the password changing.
Who fixes it, and where it runs
- Who usually fixes it
- Your hosting company
- Which plan runs it
- The Business plan
- Proof you own the site
- Needed. It asks your server for things an ordinary visitor never requests, so it waits until you prove the domain is yours.
More about this check
- Who it is about
- An intruder
- Listed under
- Things that should not be public
- The standard
- Its name in a report
config-backup-exposed
See what the free scan finds
The free scan runs 62 checks on any address, and this is not one of them: it runs on the Business plan, once you prove the domain is yours.