• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PCI Compliance - Plesk 11 Login script failing

E

EatEasy

Guest
The Plesk 11 login script is failing PCI compliance.

"The login_up.php3 web application running on this host that transmits login credentials over HTTP, which is a cleartext protocol. As such, if an attacker was able to intercept traffic containing login credentials, it would be trivial to view user account and password information.

All web application communications containing sensitive information should be transmitted using SSL/TLS (HTTPS). If re-direction from HTTP to HTTPS is utilized in an attempt to remediate this finding, please ensure that such re-direction occurs on the server side of the system (for example via the use of the HTTP "Location" header element) and that re-direction is not reliant upon the client (browser) side."

Is there a fix or workaround?
 
Last edited by a moderator:
Yes I have read and applied all the changes a few months ago and our servers have been compliant since then. This is a brand new finding with our PCI Compliance scanner. I must add that we are based in the UK and this new compliance rewquirement only became active 4 days ago.
 
I fixed this issue simply by blocking port 8880 through the Plesk firewall. It seems it is not needed unless you want to use the Plesk panel without https.
 
You must log in or register to reply here.

Similar threads

I
Issue Websocket connection failing on Plesk server
Replies
1
Views
3K
Kaspar
K
O
Question UTF-8 compliance of Plesk interface
Replies
4
Views
1K
oana.bota
O
O
Forwarded to devs Domain creation in Malayalam script fails
Replies
3
Views
992
IgorG
IgorG
O
Forwarded to devs Plesk account creation using UTF-8 credentials fails
Replies
1
Views
1K
IgorG
IgorG
X
Issue Plesk PCI Compliance Resolver - PHPmailer Openssl not working - WHMCS/Wordpress
Replies
2
Views
2K
UFHH01
U
Back
Top