Review configuration issues, exposed files and account risks with explanations that help you choose the next step.
New in FluentAuth 3.0.
This is a typical checklist review. Some fixes need a manual change.
A publicly accessible backup may expose site data. Review its location and who can reach it.
Make the recommended change, then run the check again.
Continue reviewing the other findings. One passed check is one piece of evidence.
FluentAuth evaluates the supported configuration, file exposure and account checks.
Read what the condition means and whether it applies to the way your site operates.
Apply an offered fix or follow the instructions to make the appropriate change.
Recheck the item and review the updated status before moving to the next finding.
Exposed files, unnecessary access and overlooked account risks can remain unnoticed during routine maintenance. A useful review needs to explain which conditions deserve attention and why.
FluentAuth’s checklist explains each finding and offers a fix or guidance where supported. Reviewing and addressing these items can reduce specific configuration risks. Passed checks are useful evidence, not a guarantee that the site is secure.
Know which issue to review next, what it means and how to confirm the result.
Get FluentAuth →New in FluentAuth 3.0.
Follow the setup guide →
Checks cover supported configuration and account risks. The checklist is not a vulnerability intelligence feed and does not automatically patch vulnerable plugins.
After a new build or a change of administrator, use the checklist to review the configuration together. Explain the reason for each change and keep a record of choices that depend on the site’s requirements.
No checklist can establish that. Keep WordPress and extensions updated, maintain backups and review activity. Findings give you specific checks to act on, alongside those ongoing habits.
Open the checklist and use its explanations to make informed changes.