Database privilege audit

When an extension has a SQL injection flaw, how much damage an attacker can do depends on what your site's database user is allowed to do. The Database Privileges card under Settings → Analysis reads the user's grants and flags the risky ones.

What it checks

• FILE - lets an injection read server files and write webshells.
• SUPER, CREATE USER, RELOAD, SHUTDOWN, PROCESS - powers that cover tracks, create persistent accounts or expose other queries.
• GRANT OPTION - lets the user hand its privileges to new accounts.
• Access scope - whether the user can read every database on the server rather than only this site's.

Each warning includes the exact REVOKE statement to run.

The audit is report only. Nothing is ever revoked automatically, because a wrong change can stop the site working. Run the suggested statement yourself in phpMyAdmin or your host's database tool, and keep a backup.

If it says "Could not determine"

Managed or restricted database services may hide grants or use a format the audit does not recognise. It then reports Could not determine and never a false pass - check the grants with your host.

Use Re-check grants after changing privileges; grants are read live every time.