Appearance

Knowing what is actually live

This is the smallest group in the reference, and honestly, it is here for one practical reason: knowing which theme is actually active on a site matters when something goes wrong and you need to fix it, because you need to know what you are fixing it fast. A default WordPress theme left active alongside the real theme a site actually uses is not itself a security hole. It is a sign that nobody has tidied up after development, and it usually means there is more than one theme sitting on the server that a support call, a migration, or a troubleshooting session could accidentally activate instead of the right one.

Default themes exist for a reason: WordPress needs at least one theme installed to function, and keeping the current default around as a fallback is sensible practice, not a mistake in itself. The issue is specifically when an old, unused default theme from a previous major version lingers alongside it, taking up space and adding one more thing that could get activated by accident during a panic fix at the wrong moment.

This is not a security category, and it is not trying to be one. It earns a place in this reference because “which theme is actually running this site” is a surprisingly common thing to lose track of across a portfolio built up over several years and several different developers, and the fix is simply removing what is not needed rather than anything more involved.

It is also a one-line lookup rather than anything that needs scanning the filesystem, which is why the single check in this group sits on the twice-daily snapshot alongside far more urgent checks: cheap to run is cheap to run, whatever the stakes attached to the answer.