Username: mr-wolf
TITLE
WordPress Scan stumbles on files in folder ./private
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Ubuntu 16.04 & Ubuntu 20
Plesk 18.0.30
PROBLEM DESCRIPTION
When I do a scan for WordPress instances with the new WP toolkit the scan stops after it stumbles on files that I have in the folder ./private
Those are files that are put there using FTP and have nothing to do with webhosting.
STEPS TO REPRODUCE
Scan and having a folder private with files in the folder private
I have no idea why it would scan there at all as no hosting is set to that folder
I have seen this for the first time, which is strange as the previous toolkit found wordpress instances in the strangest of places.
ACTUAL RESULT
spawns an error
EXPECTED RESULT
skip those folders
ANY ADDITIONAL INFORMATION
I would suggest to skip any folders that have their user/group not set to the website user and also skip files/folders that have limited read/write capabilities.
However... After changing all files/folders to website owner and r-attribute on all it still spawns this error.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
WordPress Scan stumbles on files in folder ./private
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Ubuntu 16.04 & Ubuntu 20
Plesk 18.0.30
PROBLEM DESCRIPTION
When I do a scan for WordPress instances with the new WP toolkit the scan stops after it stumbles on files that I have in the folder ./private
Those are files that are put there using FTP and have nothing to do with webhosting.
STEPS TO REPRODUCE
Scan and having a folder private with files in the folder private
- vhostmng-find failed: Fatal error: boost::filesystem::filesystem_error(boost::filesystem::status: Permission denied: "./private/28-08/ERWIN.galerie.7z")
I have no idea why it would scan there at all as no hosting is set to that folder
I have seen this for the first time, which is strange as the previous toolkit found wordpress instances in the strangest of places.
ACTUAL RESULT
spawns an error
EXPECTED RESULT
skip those folders
ANY ADDITIONAL INFORMATION
I would suggest to skip any folders that have their user/group not set to the website user and also skip files/folders that have limited read/write capabilities.
However... After changing all files/folders to website owner and r-attribute on all it still spawns this error.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug