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

Recent content by Hossie

  1. H

    Spam from hole in Plesk?

    I can confirm wordpress was installed on our box that was compromised. Our new mission critical production box will never again host a CMS. All old blogs are now proxy passed to trashable virtual machines. Thanks everyone.
  2. H

    Spam from hole in Plesk?

    Can you paste that code? my /tmp/sess_ was deleted (by the virus?).
  3. H

    Spam from hole in Plesk?

    JuanCar – This ‘virus’ uses the system call to send mail. This means that all emails the ‘virus’ sends are passed to Qmail. It does NOT try to open a port/socket and act as its own MTA. Thus the only useful thing you can do with Iptables is to completely block outbound dport 25. Your example...
  4. H

    Spam from hole in Plesk?

    We have a very similar issue. OS: CentOS release 5.8 (Final), plesk psa-9.5.2-cos5.build95100504.10 Running litespeed, qmail, php, multiple vhosts (some have wordpress but we are not sure if this is the exploit path). The server was bogged down with the email spam blast. I stopped qmail so...
  5. H

    Spam from hole in Plesk?

    We have a very similar issue. OS: CentOS release 5.8 (Final), plesk psa-9.5.2-cos5.build95100504.10 Running litespeed, qmail, php, multiple vhosts (some have wordpress but we are not sure if this is the exploit path). The server was bogged down with the email spam blast. I stopped qmail so...
See more
Back
Top