• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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