• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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