TITLE:
High risk bug report | Wordpress Extension copying unknown database credentials
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:Onyx 17.8 | Debian 8.11
PROBLEM DESCRIPTION:Hello,
as it wasn't possible to submit a support ticket, as I have a license from a plesk reseller, I publish it here:
On my server I have experienced 2x a critical issue.
When cloning Wordpress data (using Wordpress management extension) from an instance to a newly created one, this happens:
- one (was always different) out of about 15 Wordpress instances gets a new wp-config.php placed where the old one was and replaces it
- the one chosen instance was neither source, nor destination of cloning
- it contains genuine (working!) wordpress database credentials from an unknown wordpress installation from a different country?!
---
Question:
Additionally to this high risk bug, I would like to know, where the Wordpress extension is syncing my config files to?! It should never leave my server.
My server is based in Germany and the wp-config-file which was placed, belongs to an IP-address in Canada. I doubt a Canadian is using a German server for his website. So I suppose Plesk is syncing it somewhere.
Best regards
STEPS TO REPRODUCE:as it wasn't possible to submit a support ticket, as I have a license from a plesk reseller, I publish it here:
On my server I have experienced 2x a critical issue.
When cloning Wordpress data (using Wordpress management extension) from an instance to a newly created one, this happens:
- one (was always different) out of about 15 Wordpress instances gets a new wp-config.php placed where the old one was and replaces it
- the one chosen instance was neither source, nor destination of cloning
- it contains genuine (working!) wordpress database credentials from an unknown wordpress installation from a different country?!
---
Question:
Additionally to this high risk bug, I would like to know, where the Wordpress extension is syncing my config files to?! It should never leave my server.
My server is based in Germany and the wp-config-file which was placed, belongs to an IP-address in Canada. I doubt a Canadian is using a German server for his website. So I suppose Plesk is syncing it somewhere.
Best regards
- Create a new subscription
- Go to Wordpress management extension
- Clone an old subscription to the newly created one
- Ovewrite files, if needed
- Run cloning
Not sure, if it happens always.
ACTUAL RESULT:- Go to Wordpress management extension
- Clone an old subscription to the newly created one
- Ovewrite files, if needed
- Run cloning
Not sure, if it happens always.
Independent Wordpress instance on my server gets a new wp-config.php file from an unknown, but genuine, source.
Old file get's overwritten.
EXPECTED RESULT:Old file get's overwritten.
This should not happen.
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:Answer the question