Security issue: DB restore breaks because of a join in unpaid_hours table

  • ‘unpaid_hours’ table uses a view that depends on core ‘users’ table. Trying to backup and restore the database fails, because when unpaid_hours table definition is loaded, users table doesn’t exist yet.

    It’s a triple issue:
    1° of course the impossibility to back up and restore the database easily is a huge bug and a security issue
    2° the message is that ‘users’ table does not exist, it is not easy to find that the guilty table is actually unpaid_hours
    3° WP Hourly tables are not deleted when the plugin is uninstalled (so the bug persists even if the plugin is not there anymore)

    While there are workarounds for backup/restore (table by table) I am pretty sure this makes any backup/migration plugin or automation fail or end up with an unreliable dump (and this is why I mark it as a security issue).

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Security issue: DB restore breaks because of a join in unpaid_hours table’ is closed to new replies.