#068Technical4 min
Check a MySQL database’s security
Review MySQL or MariaDB accounts, host restrictions, file capabilities and connection settings through an authorized read-only audit.
Hackaiz team · updated 21/11/2026

01Review accounts and settings, not table records
The MySQL / MariaDB live check focuses on the server’s security configuration. It asks about accounts, privileges and selected settings through one connection. It does not browse customer tables, export orders or change records. This is a practical way to raise configuration questions with the administrator, not a replacement for testing your application’s own access decisions.
Choose the environment deliberately. A demonstration server and a production server may share a database name while having different users and connection rules. Confirm the host and database before submitting an address. The returned server version helps explain compatibility issues, particularly when a query supported by one MySQL or MariaDB version is unavailable on another.
02Add the MySQL connection safely
Open “Choose a database” from the connection flow and find “Live Postgres and MySQL”. Choose “MySQL / MariaDB”, not PostgreSQL. The address example starts with mysql:// and includes the account, password, host, port and database. Have your administrator prepare a dedicated read-only account rather than sharing the account used to administer the whole server.
The saved address is encrypted and never displayed back to you. You must confirm ownership before saving it. A database on a private network cannot be reached through this direct flow. If a connection fails, distinguish refused credentials from an unreachable host. Neither failure means that the server has passed its security check, and neither justifies removing necessary network restrictions.
- 1Enter the connection address for the authorized MySQL or MariaDB target.
- 2Check “I own this database and allow Hackaiz to check it.” and click “Save”.
- 3Choose “Select” in the analysis picker, or “Check my database” when using the direct-check view.
03Read account findings in their network context
The audit looks for anonymous users and accounts with no password. Its no-password query excludes certain socket-based or non-login authentication plugins, so this is not a simple assumption that every empty password field is exploitable. Another check identifies older password plugins. Ask the administrator what authentication method the application actually uses before planning a migration.
Host restrictions are important in MySQL because a user is associated with an allowed host. A host of %, 0.0.0.0 or :: triggers the broad-host check. That finding describes the account configuration, not proof that a firewall allows connections from everywhere. Review both layers. The audit also checks for powerful server-wide privileges on non-system accounts, including SUPER, FILE, GRANT and SHUTDOWN capabilities. An application account normally deserves a different discussion from a maintenance account.
04Review file access, encryption and remaining limits
The settings checks include local_infile and secure_file_priv. These relate to local-file loading and restrictions on file import or export. A warning is a reason to ask which operational process needs the capability and whether it can be constrained. During the audit, Hackaiz disables the client capability that would let the server request a local file. It does not test file access by reading your documents.
Other queries look for accounts whose connection configuration does not require encryption and demonstration databases named test, sakila or world. A sample database is not proof of compromise. Likewise, a connection-encryption warning should be reviewed against the intended account and deployment, rather than treated as a complete inventory of all network protection.
Check the count of queries not run before concluding that no issue was found. Access to mysql.user may be restricted, and version differences can make a query fail. Keep those questions open for the administrator; do not grant unrestricted access merely to obtain a cleaner result. Database audits use credits. Corrections to server accounts or settings remain under human control: Hackaiz does not write changes to the connected database. After testing an approved correction, repeat the relevant check and compare the named account or setting.
Frequently asked questions
Take the next step
Was this article helpful?