Database integrity
How the database is named, who connects to it, and what else it can reach.
31 checks in this group, 19 with a full write-up.
The database is not just your data
Most of the checks in this group are about limiting what a single compromise can reach, not about protecting content from being lost. A default table prefix (jos_ or wp_) is not a secret, it is a convenience for anyone writing a generic SQL-injection payload that assumes it and gets to skip the step of finding out. A database user with root privileges, or one scoped across every database on the server rather than just the one it needs, turns “this site’s database got compromised” into “every site sharing that server’s database got compromised”, which on shared or reseller hosting is a realistic blast radius rather than a theoretical one. How to check Joomla database security walks through the full picture, including the questions this group’s automated checks do not ask on their own.
The rest of the group is about drift between what the CMS expects and what is actually sitting in the tables: a schema that is behind the version the CMS thinks it is running, backup tables an old migration or a nervous developer left behind and never dropped, pending migrations that never completed. None of these are attacks. They are the database equivalent of the configuration drift elsewhere in this reference, quiet enough that nothing breaks obviously, until an update assumes a column exists that a stalled migration never added.
On a portfolio of sites built up over years by different people, database hygiene is one of the places where the gap between “was fine at launch” and “still fine now” opens widest, because nobody looks at table structure unless something visibly breaks. A user action log nobody purges, growing without limit, is the same story: harmless until the table is large enough to slow every query that touches it. None of this needs a file-by-file scan to detect, which is why every check in this group runs on the twice-daily snapshot rather than waiting on a longer audit cycle.
The table checks look at how the database itself is holding up. Tables not using InnoDB are on an engine with no crash recovery, tables not using utf8mb4 cut off emoji and some languages on save, and crashed database tables fail every read and save until they are repaired. Tables from another install are old copies or staging sites sharing the same database, and database size and largest tables shows where the space goes, for information only.
On Joomla, the content checks find rows that no longer join up: items left checked out that no one else can edit, menu items for uninstalled components that lead to an error page, articles in a missing category that no category list shows, and orphaned asset rows where permissions and content have gone out of step. Items in the trash is a count rather than a warning: what is waiting to be deleted, and a safe way to empty it.
Joomla
Default Database Prefix Should Not Be Set As jos_
jos_ was Joomla's fixed table prefix in early versions, so keeping it makes every table name guessable, one less obstacle an SQL injection has to clear.
Database User Should Not Be "root"
A root database user turns one SQL injection into access to every database on the server, not just this site's.
0.1% of the Joomla sites we have this data for fail it
DB User Should Only Have Access To One Database
If your database credentials can also see other databases on the server, one SQL injection on this site can reach every database that user has access to.
Backup Tables Should Be Removed From Database
Tables left over from a backup or migration, typically prefixed bak_, sit in the same database as your live data, so a compromise of one exposes the other too.
0.5% of the Joomla sites we have this data for fail it
Joomla Core Database Schema Should Match Installed Joomla Version
The #__schema table records which database updates have run, and a mismatch against your Joomla version means an upgrade left tables only partly migrated.
Expire Old User Action Log Entries
Joomla's action log records logins and configuration changes but never expires entries by default, so without a purge it grows indefinitely unread.
Action Log Tables Should Not Grow Unchecked
Joomla's User Action Log records every login and configuration change and, unless a purge is enabled, keeps all of it forever. Nothing on the site ever reads it back, so it quietly becomes one of the largest tables in the database and slows every backup and migration that has to copy it.
Lists articles, modules, menu items and other rows Joomla still has locked for editing, so nobody else can change them until they are checked in.
Lists this site's database tables on MyISAM or another engine with no crash recovery, where a server crash can lose or corrupt data.
Lists this site's database tables whose collation is not utf8mb4, so emoji and some scripts are cut off or rejected on save.
Lists this site's database tables the database server cannot open, so every read and save on them goes wrong until they are repaired.
Tables From Another Install In This Database
Counts tables in the same database that belong to a different prefix, such as an old copy or a staging install, so one break-in can reach both.
Database Size And Largest Tables
Reports how much space this site's own tables take, data plus indexes, and which ten are largest. For information only, so it never warns.
Menu Items For Uninstalled Components
Lists site menu items that still open a component that is no longer installed, so visitors who click them get an error page.
Articles In A Missing Category
Lists articles whose category was deleted, so they drop out of every category list and blog on the site.
Lists permission rows left behind by deleted articles, categories and modules, and articles or categories with no permission row at all.
Counts the articles, categories, modules and menu items in Joomla's trash, and empties it the way Joomla does.
Content With A Deleted Author
Lists articles, categories and other content whose author account was deleted, which Joomla will not let anyone save until the author is changed.
Articles Missing From Article Manager
Lists articles that exist on the site but Joomla's Article Manager cannot show, because their workflow records are missing, and rebuilds those records.
Smart Search Menu Items Missing
Reports Smart Search items missing from the Joomla administrator menu, which stops anyone reaching the component, and recreates them.
Smart Search Tables Missing
Reports the Smart Search working tables missing from the database, which makes indexing fail, and recreates them.
WordPress
Default Database Prefix Should Not Be Set As wp_
Checks whether your tables still use the default wp_ prefix, which lets an attacker with partial access guess table names instead of having to find them.
Database User Should Not Be "root"
A root database user turns one SQL injection into access to every database on the server, not just this site's.
0.1% of the WordPress sites we have this data for fail it
DB User Should Only Have Access To One Database
Checks how many databases your MySQL credentials can see: if one is compromised, broader access means every other database on the account is exposed too.
The mySites.guru Activity Log Table Should Not Grow Unchecked
WordPress keeps no activity log of its own, so this reports one table and one only: bf_activitylog, which our connector writes on your site. It gains rows on every snapshot, audit and connector upgrade, nothing on the site ever reads them back, and left alone it grows for as long as the site stays connected.
Pending Database Migrations
Checks whether WordPress core has pending database schema updates it has not yet run, which can leave the site behaving inconsistently after an update.
0.1% of the WordPress sites we have this data for fail it
Lists this site's database tables on MyISAM or another engine with no crash recovery, where a server crash can lose or corrupt data.
Lists this site's database tables whose collation is not utf8mb4, so emoji and some scripts are cut off or rejected on save.
Lists this site's database tables the database server cannot open, so every read and save on them goes wrong until they are repaired.
Tables From Another Install In This Database
Counts tables in the same database that belong to a different prefix, such as an old copy or a staging install, so one break-in can reach both.
Database Size And Largest Tables
Reports how much space this site's own tables take, data plus indexes, and which ten are largest. For information only, so it never warns.
Find out which of these your sites fail
Connect a site and every check in this group runs against it automatically, with the result and the fix in one place. These run twice a day on every connected site.
Run a free audit