• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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