Attackers exploited SimpleHelp's OIDC authentication flaw, CVE-2026-48558, in 2026. Ransomware operators also exploited older SimpleHelp vulnerabilities and used the software for persistence after other intrusions. If you run a server, check your version and authentication settings, install the vendor updates, then investigate earlier access using the checks below.
Jump to the stepsDo the vendor steps on this page first. Then use our Secure SimpleHelp playbook for step-by-step guidance to secure your self-hosted server. It adds to patching and incident response. If you find unauthorized activity, investigate the affected machines before you rely on the server again.
Blackpoint documented attackers exploiting CVE-2026-48558 to get a technician session, then deploying TaskWeaver and Djinn Stealer. Microsoft linked older SimpleHelp flaws to Medusa ransomware operations. Other investigators saw attackers install SimpleHelp after getting in some other way, so SimpleHelp on an endpoint doesn't tell you how the intrusion started.
Horizon3 discovered the OIDC flaw on May 21 and reported it May 22. SimpleHelp dates patched releases to May 26; Horizon3 disclosed the issue June 12. Blackpoint's June 29 investigation confirmed exploitation. CISA added CVE-2026-48558 to its Known Exploited Vulnerabilities catalog that day, with ransomware use marked Unknown.
Horizon3 counted about 3,400 internet-exposed SimpleHelp servers in January 2025 and nearly 14,000 in a June 2026 Shodan snapshot. Those are exposed servers, not compromised ones.
CVE-2026-48558 lets an unauthenticated attacker forge an identity and get a technician session, because vulnerable OIDC login code doesn't check token signatures. Versions 5.5.0 through 5.5.15 and 6.0 prereleases before RC2 are affected. You are exposed only if OIDC is enabled for a Technician Group with Allow group authenticated logins turned on.
The CVE record rates it CVSS 3.1 10.0 and CVSS 4.0 9.5. The vendor says servers without OIDC, or without that group-login setting, cannot be exploited this way. Whether MFA can be bypassed depends on your configuration. Check the vendor's advisory against your own setup.
The three CVEs carry 2024 identifiers, but Horizon3 disclosed them in January 2025. Sophos linked an MSP incident involving DragonForce to these flaws with medium confidence. Microsoft's April 2026 report identifies all three among vulnerabilities exploited by Storm-1175, a Medusa operator. CISA marks their ransomware use as Known.
CISA's June 12, 2025 advisory AA25-163A describes likely exploitation of CVE-2024-57727 against a utility-billing provider's downstream customers. It does not name a ransomware family.
Check your installed version and back up the installation before updating. Use the vendor's update procedure for your platform, then verify the result. Change administrator and local-technician passwords and replace API tokens as part of remediation. Review technician accounts, including group-authenticated users. Preserve evidence first if you suspect compromise.
/allversions, inspect the version near the top of configuration/serverconfig.xml, or open Administration > Overview > Check for Updates.20261015-000736, so check the release list and pick a current version.Patch 070125 in the server log. The version number alone doesn't prove the patch is installed.Update > Release. On Windows, run the new installer. For manual Linux/macOS updates, stop the server, extract into a separate directory, restore configuration and restart. Do not merge installation directories.It depends on your own server. SimpleHelp runs on infrastructure you or your provider operate, so the fixes only help once someone installs them. Confirm both the 2026 and the January 2025 fixes, then review technicians, credentials and endpoints. An update won't tell you whether attackers got in before you installed it.
Start with unfamiliar technicians and configuration changes, then check the machines those accounts could reach. The vendor and Horizon3 publish account and log checks; CISA adds endpoint and agent-configuration guidance. Preserve server and Remote Access service logs before cleanup. Finding no suspicious entries in a first pass does not prove the environment is clean.
Administration > Technicians > gear icon > Show Group Authenticated Users. Investigate identities your team cannot explain.Administration > Server > Server Log. Search registration and configuration-save entries for unknown identities and New Anon. The vendor says that marker can indicate legitimate group-authenticated account creation; check authorization.serviceconfig.xml beneath JWrapper-Remote Access/JWAppsSharedConfig/. Investigate unfamiliar server addresses in <ConnectTo entries and unexpected API tokens.aaa.exe created after January 2025. Blackpoint observed node.exe executing downloaded jquery.js. Treat these as investigation leads, not an exhaustive detection set.Attackers install or reconfigure SimpleHelp clients to maintain remote access after gaining entry. Field Effect found configuration changes authorizing an attacker-controlled server. Arctic Wolf observed renamed SimpleHelp clients following suspected BeyondTrust exploitation, while Huntress documented SimpleHelp as a redundant access channel. Investigate those endpoint installations even if your own server is patched.
Field Effect also observed administrator-account creation and Sliver persistence. Huntress reported attempted Crazy ransomware deployment in January-February intrusions. Scope the other access mechanisms before closing the incident.
Use the Secure SimpleHelp playbook for step-by-step guidance after patching and investigation. It is a $79 one-time PDF for self-hosted servers, with free email support on the solution at support@threatlistpro.com and updates through the same download link. There are no refunds, so check the product details before buying.
We built this method on our own ScreenConnect server; this edition applies the same method to SimpleHelp servers, but we have not tested it on SimpleHelp.
SimpleHelp fixed CVE-2026-48558 in 5.5.16 and 6.0 RC2; the vendor also identifies final 6.0 and later as unaffected by this flaw. Affected versions include 5.5.0 through 5.5.15 and earlier 6.0 prereleases. These are minimum fix thresholds. Check the vendor release list before choosing your deployment version.
The vendor says configurations without OIDC cannot be exploited through the documented account-creation attack. The attack requires an enabled OIDC authentication service, that service enabled for a Technician Group, and Allow group authenticated logins enabled for that group. Review those settings alongside your installed version when assessing exposure.
Yes. Blackpoint documented exploitation of CVE-2026-48558 to obtain a technician session, followed by TaskWeaver and Djinn Stealer deployment. Microsoft also identified older SimpleHelp vulnerabilities among those exploited by the Medusa operator Storm-1175. Investigators documented separate cases where attackers installed SimpleHelp after gaining access through another product.
Sophos reported attackers using an MSP-operated SimpleHelp instance to reach customers, steal information and deploy DragonForce ransomware. Sophos said, with medium confidence, that the attackers got in through the three vulnerabilities disclosed in January 2025. The exact entry route is not confirmed. CISA's separate advisory on a utility-billing provider did not name a ransomware family.
Updating addresses the documented flaws, but you still need to investigate earlier access. Review unfamiliar technicians and configuration changes, then examine affected endpoints. The vendor recommends changing administrator and local-technician passwords and replacing API tokens as part of remediation. Preserve evidence before cleanup if you suspect someone accessed your server.
No. The vendor explains that New Anon can indicate account creation through group authentication. Check whether your team authorized the identity and compare registration or configuration-save entries with technician records. Horizon3 recommends showing group-authenticated users when hunting on affected deployments. Investigate unfamiliar accounts before deciding whether the activity was malicious.
Yes. Attackers can install legitimate SimpleHelp clients after gaining access through another route and use them for persistence. Arctic Wolf documented renamed SimpleHelp clients after suspected BeyondTrust exploitation. Huntress observed SimpleHelp as a redundant access channel in ransomware intrusions. Check endpoint installations and their registered servers alongside your own console.
Research cutoff: November 15, 2026.
ScreenConnect and BeyondTrust incident guidance and self-hosted security playbooks.