Scans your WordPress installation for security vulnerabilities.
No. Acunetix WP Security needs to be left activated to work. Version hiding, turning off DB errors, removing WP ID META tag from HTML output, and other functionality will cease if you deactivate the plugin.
From the Linux command line (for advanced users): chmod xxx filename.ext (replace xxx with with the permissions settings for the file or folder).
From your FTP client: Most FTP clients, such as FileZilla, etc, allow for changing file permissions. Please consult your client's documentation for your specific directions.
No, the Acunetix WP Security plugin when running in a MultiSite installation can only be network activated. It cannot be activated per individual sites. All its features are related to the whole network and activating it per individual sites would be pointless.
For more information, please visit http://codex.wordpress.org/Changing_File_Permissions
Many attackers and automated tools will try and determine software versions before launching exploit code. Removing your WordPress blog version may discourage some attackers and certainly will mitigate virus and malware programs that rely on software versions.
For more information on the Acunetix WP Security plug-in and other WordPress security news, visit the Acunetix Blog and join our Facebook page. Post any questions or feedback on the Acunetix WP Security plug-in forum.
Requires: 3.0 or higher
Compatible up to: 4.2.10
Last Updated: 2 years ago
Active Installs: 100,000+
0 of 1 support threads in the last two months have been marked resolved.
Got something to say? Need help?