• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Wp toolkit question

garry414

New Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
18.0.56 #2
I updated all the suggested security measures in wp-toolkit. I check a few days later and a couple were suggested again. Is that the nature of the beast of wp toolkit to check for updates or should that be a one and done?
I’m also running Wordfence premium so I’m not sure if that overlaps.
My concern is if I have a breach changing those security measures or if plugin updates or something else can cause wp-toolkit to require repeated securing?
 
WP Toolkit performs regular scans. What I would assume is that the option(s) in question get reverted back to the original state, hence, detected as vulnerabilities again. What I can suggest is to test the behavior on a fresh WordPress installation and confirm if the behavior reappears. Also, it seems like you are currently on a unsupported Plesk version, so I would strongly recommend upgrading to a newer version as soon as possible. If the issue still continues, you may provide us with examples on what options seem to be resetting and we will check further if the behavior is recognized as a bug.
 
Back
Top