Your MSP Is the Target: ScreenConnect Exploits and Default Passwords Are Hitting Small Businesses Right Now
Two stories from this week’s vulnerability intelligence deserve your full attention. One is a confirmed, actively-exploited vulnerability in software that your IT support provider almost certainly uses to access your systems. The other is a pattern so fundamental it should make anyone responsible for a business’s IT provision deeply uncomfortable: hardcoded default passwords, scoring CVSS 9.8, shipping in production software in November 2026.
Neither of these requires you to be technically sophisticated to understand. Both of them require you to act.
The ScreenConnect Exploit: When Your MSP Becomes the Attack Vector
ConnectWise ScreenConnect is remote access software. It is the tool that allows your IT support company, your managed service provider (MSP), to connect to your computers and servers without being physically present. It is ubiquitous in the managed services industry. The majority of UK SMBs who outsource their IT will have an MSP that uses it.
On the 8th of September 2026, ConnectWise disclosed CVE-2026-84869 with a CVSS score of 9.9 out of 10. Three days later, on the 11th of September 2026, CISA added it to the Known Exploited Vulnerabilities (KEV) catalogue. The KEV catalogue is not a list of theoretical risks. It is CISA’s confirmation that a vulnerability is being used by real attackers against real targets in the real world.
Huntress, a security firm that works extensively with MSPs, has now published confirmed evidence of that exploitation: attackers are using CVE-2026-84869 to run malicious files specifically on MSP technician accounts.
This is the part that matters most to a small business owner. The attack is not aimed at you directly. It is aimed at the person who has the keys to your systems.
An MSP technician account has administrative access to dozens, sometimes hundreds, of client environments. When an attacker compromises one of those accounts through a vulnerability in ScreenConnect, they do not get one business. They get every business that technician supports. Your data. Your client records. Your financial systems. All of it, accessible through a single compromised account at a third party you may never have asked about.
This is the supply chain attack model. It is not new. It has been the dominant attack pattern against SMBs for several years. What is new is the specific, confirmed exploitation of this particular vulnerability, right now, against the tool your IT company almost certainly relies on.
The Default Password Problem: Still Here in 2026
Separate from the ScreenConnect story, two vulnerabilities published to the NIST National Vulnerability Database on the 16th of November 2026 illustrate a failure so basic it is almost insulting.
CVE-2026-129955 affects NodePress through version 8.5.1. The vulnerability description is concise: unauthenticated attackers can gain administrator access by using the hardcoded default password ‘root’. Specifically, an attacker can send the base64-encoded string ‘root’ to the admin login endpoint when the administrator has not changed the default password, and receive full admin tokens in return. CVSS score: 9.8.
CVE-2026-129952, also affecting NodePress through version 8.5.1, compounds this. The software contains a hardcoded fallback JWT (JSON Web Token) signing key with the value ‘nodepress-secret’. An unauthenticated attacker can forge administrator tokens using this key and gain full control of the content management system, including article management, file management, and configuration access. CVSS score: 9.8.
NodePress is a blogging and content management platform. It is the kind of software that small businesses and sole traders use to run websites. The vulnerabilities exist because the software shipped with a known, public default password and a known, public cryptographic key, neither of which force a change on first use.
This is not a novel attack technique. It is not an advanced persistent threat. It is an attacker trying ‘root’ and succeeding. The fact that two critical vulnerabilities of this type were published in the same 24-hour window is not a coincidence; it is a symptom of an industry that continues to treat security as an afterthought in development.
For the SMB owner, the lesson is not specific to NodePress. It is a general principle: any software that ships with a default password or default credential of any kind must have that credential changed before the system is connected to the internet. This applies to routers, NAS devices, CMS platforms, database management tools, and anything else in your environment.
Why These Two Stories Connect
On the surface, an MSP remote access exploit and a CMS default password vulnerability look like separate issues. They are not. They are both expressions of the same underlying problem: trusted access being left insufficiently protected.
In the ScreenConnect case, the trusted access is the MSP’s administrative connection to your systems. In the NodePress case, the trusted access is the administrator account on a web platform. In both cases, the attacker’s goal is the same: obtain legitimate-looking credentials or session tokens, then operate inside the environment without triggering obvious alarms.
This is why the NCSC consistently emphasises privileged access management alongside patching. It is not enough to fix the vulnerability after the fact. The question is what controls exist to limit the damage when a privileged account is compromised, because compromises will happen.
For the small business that outsources its IT: the question is not whether your MSP has patched ScreenConnect. The question is what happens to your data if they haven’t, and whether you would even know.
How to Turn This Into a Competitive Advantage
Businesses that ask their MSP hard questions about patching cadence and technician account security are, in practice, selecting for better MSPs. The act of asking is itself a filter.
If your MSP can answer the questions in the next section fluently and without hesitation, that is a signal worth noting. If they deflect, go vague, or tell you it’s too technical to explain, that is also a signal worth noting.
In client-facing industries, being able to tell a prospect or client that you actively manage your IT supply chain security, including asking your MSP to demonstrate their own security posture, is a differentiator. Cyber Essentials certification requires you to have managed software and patching in scope. Extending that scrutiny to the tools your IT provider uses is consistent with that standard and goes beyond the checkbox.
How to Sell This to Your Board
Three arguments that will land with a senior decision-maker or board:
The MSP risk is unquantified today. You almost certainly do not know what access your IT provider’s tools have to your systems at this moment, what accounts hold that access, or whether those accounts are protected by multi-factor authentication. That is an unaudited risk sitting at the boundary of your environment. The ScreenConnect story makes it concrete: this is not theoretical exposure, it is confirmed active exploitation.
A supply chain breach bypasses most of your existing controls. Firewalls, endpoint protection, and email filtering are all built on the assumption that the attacker is an outsider trying to get in. When the attacker is using a legitimate MSP tool and a legitimate MSP account, those controls do not fire. The damage happens inside your defences. This is why supply chain attacks are increasingly the preferred method against SMBs.
The cost of asking is zero. You are not being asked to spend money today. You are being asked to send three questions to your IT provider. The cost of not asking, if the answer turns out to be that they haven’t patched and don’t have MFA on technician accounts, is potentially the cost of a full ransomware recovery.
What to Do by Friday
These are specific, actionable steps. None of them require technical expertise to initiate.
1. Contact your MSP and ask three questions in writing. Have you applied the patch for CVE-2026-84869 in ConnectWise ScreenConnect? Do all technician accounts that can access my systems require multi-factor authentication? How would you notify me if your tools were used to access my systems without authorisation? Ask for written confirmation. The act of asking creates a paper trail and signals that you are paying attention.
2. If you run any web platform, CMS, or internet-connected software with an admin panel, verify the default credentials have been changed. This includes routers, NAS devices, WordPress installs, any CMS, and any database management interface. If you are not sure how to check, ask your IT provider, specifically whether they can confirm default credentials have been changed on all managed systems.
3. Ask your MSP what their own patch management SLA is. A serious MSP will have a documented process for applying critical patches to their own tooling. CISA added CVE-2026-84869 to the KEV catalogue on the 11th of September 2026. It is now the 17th of November 2026. If they cannot confirm the patch was applied within 14 days of the KEV listing, that is a gap worth discussing.
4. Request your MSP’s most recent security self-assessment or Cyber Essentials certificate if they hold one. A supplier who handles administrative access to your systems is a high-risk supplier in data protection terms. You are entitled to ask about their security posture. If they refuse or cannot provide anything, treat that as material information.
5. Add MSP security to your next board or senior management agenda. Not as a standing agenda item, but as a one-time review: who has administrative access to our systems, through what tools, protected by what controls. That review, done once and documented, puts you in a materially stronger position than most comparable businesses.
The podcast companion to this article goes through the top-line findings. If you found it useful, follow the show wherever you listen, leave a rating or a review, drop a comment with your thoughts, and share it with another business owner who needs to hear this. The more people who start asking their MSPs these questions, the better the industry gets.