• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Security issue: Reseller account pwd is exposed to customers

N

Nayabk

Guest
Hello Folks,
We just discovered a security flaw in Plesk and Sitebuilder. This needs to be addressed immediately as it can impact a lot of your customers including us.

Please install Fiddler or some other HTTP/HTTPS debugging proxy to see the problem.

Repro Steps:
Create a Reseller account in Plesk (lets say 'reseller1')
For this reseller create a new customer account (domain admin). Lets call him 'customer1'

Either go to a new machine or on this machine clear browser cookies, history etc. and log in as 'customer1' in Plesk.
Enable Fiddler to look at the browser traffic.
In Plesk go to 'SiteBuilder Wizard" for this customer.
In Fiddler look for a call to ExternalLogin.ashx. Look under Session Inspector->WebForms and you'll see the form's Post data including Login and Password. The login & password will be that of reseller1 and NOT customer1.

Folks, you've to take care of this immediately. You're exposing all reseller's passwords to their customers.
 
We could not reproduce this so far. Plesk uses the login of the exact user logged in now.
Could you please let us know the exact Plesk build number?
 
Back
Top