Secure SimpleHelp playbook for self-hosted servers
Secure your self-hosted SimpleHelp server with a step-by-step PDF. We built this method on our own ScreenConnect server; this edition applies the same method to SimpleHelp servers. We have not tested it on SimpleHelp.
One-time payment. Instant PDF download. No refunds.
- For self-hosted SimpleHelp servers only.
- SimpleHelp-specific instructions, with preparation and testing.
- Rollback steps so you can reverse your changes.
- Free email support on the solution.
Why review SimpleHelp security now?
Attackers exploited SimpleHelp's 2026 authentication bypass, and ransomware operators have exploited its older flaws. A June 2026 Shodan snapshot reported by Horizon3 found nearly 14,000 SimpleHelp servers exposed to the internet. If you run one, confirm your updates and check for signs of earlier access.
- The 2026 flaw: CVE-2026-48558 lets an unauthenticated attacker get a technician session on servers with a vulnerable OIDC setup. It is rated CVSS 3.1 10.0. Versions 5.5.0 through 5.5.15 are affected, and the fixes are 5.5.16 and 6.0 RC2. Your server is only exposed this way if OIDC is enabled for a Technician Group that allows group-authenticated logins (vendor guidance).
- Confirmed exploitation: Blackpoint's June 29 report documents attackers using CVE-2026-48558 to get in, then deploying TaskWeaver and Djinn Stealer. CISA added the flaw to its Known Exploited Vulnerabilities catalog the same day (Blackpoint investigation).
- Ransomware against an MSP and its customers: Sophos reported attackers using an MSP-operated SimpleHelp instance to steal data and deploy DragonForce ransomware in customer environments. Sophos assessed exploitation of CVE-2024-57726, CVE-2024-57727 and CVE-2024-57728 with medium confidence (Sophos investigation).
- The older flaws remain relevant: Microsoft identifies those same three CVEs among the vulnerabilities exploited by Storm-1175, a Medusa ransomware operator. Although their identifiers say 2024, researchers disclosed the flaws in January 2025 (Microsoft investigation, original disclosure).
The 14,000 figure counts exposed servers, not compromised ones (Horizon3, June 12, 2026). Read the free guide for the timeline and vendor response steps: SimpleHelp attacks in 2026.
Where did this method come from?
We built it on our own on-premises ScreenConnect server after we found rogue unattended sessions on it. Since we applied the method, we have seen no new rogue sessions and no brute-force login attempts. That is what we saw on one server. It is an observation, not proof.
The SimpleHelp attacks prompted us to apply the same method to SimpleHelp servers in this edition, using SimpleHelp's documentation for the product-specific instructions.
We have not tested the method on SimpleHelp. We still patch our own server and follow the vendor’s guidance, and you should too.
What is in the SimpleHelp playbook?
You get a step-by-step guide for applying the method to a self-hosted SimpleHelp server, from preparation through testing. Start with the fit check before making changes. Then follow the instructions, confirm that your support work still functions, and use the rollback steps if you need to reverse a change.
- Our ScreenConnect experience and its limits
- The SimpleHelp attacks and vendor response guidance
- A fit check for your deployment
- A preparation checklist before making changes
- The step-by-step method for self-hosted servers
- SimpleHelp-specific instructions
- Checks to confirm your support work still functions
- Rollback instructions
- Ongoing maintenance
- A checklist for suspected compromise
Is the SimpleHelp playbook right for your deployment?
It fits if you run your own SimpleHelp server and want a step-by-step way to secure it on top of the vendor patches. Plan time to prepare and to test your support work afterward. It does not clean up an intrusion, and we have not tested it on SimpleHelp. Check these points before you buy.
- Self-hosted SimpleHelp only. That means a server you run, on premises or on infrastructure you manage.
- Keep patching. Follow SimpleHelp's update guidance. The 5.5.8 fix for the January 2025 flaws does not fix the 2026 OIDC flaw.
- It does not remove an existing compromise. If you suspect an intrusion, preserve evidence and get incident response help. Applying the playbook won't tell you whether your server or managed endpoints are clean.
- No refunds. Confirm that you run your own SimpleHelp server before purchasing.
Secure SimpleHelp Playbook
One-time payment. No refunds.
- For self-hosted SimpleHelp servers only
- PDF, instant download
- Free email support on the solution: support@threatlistpro.com
- Updates to this edition through the same download link
FAQ
Have you tested this method on SimpleHelp?
No. We built this method on our own on-premises ScreenConnect server after finding rogue unattended sessions. We have seen no new rogue sessions or brute-force login attempts since applying it. That is one server's observation. This edition applies the same method to SimpleHelp servers; we have not tested it on SimpleHelp.
Which SimpleHelp deployments does this cover?
This edition covers self-hosted SimpleHelp servers that you run, on premises or on infrastructure you manage. You get SimpleHelp-specific instructions for applying the method, with preparation, testing and rollback. If someone else runs your server for you, ask them before you buy, because there are no refunds.
Does this replace patching or remove an existing compromise?
No. Keep applying SimpleHelp updates and follow the vendor's investigation guidance. Use the playbook as an extra security layer. It does not remove an existing compromise or confirm that your server is clean. If you suspect an intrusion, preserve evidence and get incident response help before treating the server as secure.
Can I get help applying the playbook?
Yes. Your purchase includes free email support on the solution in the PDF. Write to support@threatlistpro.com with questions about applying the steps to your setup. The playbook also covers testing and rollback so you can check your changes and reverse them if you need to.
What do I get for $79?
You get the Secure SimpleHelp Playbook as an instant PDF download after checkout. You pay $79 once. There are no refunds. Updates to this edition use the same download link. Free email support on the solution is included at support@threatlistpro.com. Check the self-hosted scope before buying.
Also from ThreatListPro: the ThreatListPro blocklist for VPN brute force protection. It is a separate product: 5.4M+ IPv4 addresses, checked for new attackers every 6 hours.
Sources
- SimpleHelp: CVE-2026-48558, affected configurations and fixed releases
- Horizon3: June 12, 2026 authentication-bypass disclosure, investigation guidance and exposure snapshot
- Blackpoint: confirmed CVE-2026-48558 exploitation followed by TaskWeaver and Djinn Stealer
- Horizon3: January 2025 disclosure of CVE-2024-57726, CVE-2024-57727 and CVE-2024-57728
- Sophos: DragonForce attack against an MSP and customers, with medium-confidence exploit-chain assessment
- Microsoft: Storm-1175 and Medusa ransomware operations, including exploitation of the three older SimpleHelp flaws
- SimpleHelp: server update procedures