Arcadian Digital

How long does your business have between a security fix going out and attackers using the flaw it fixes? If the past few weeks are anything to go by, it’s often less than a week. Sometimes it can be a matter of hours.

For a long time, updating a website once a quarter felt like a reasonable maintenance schedule. Looking at the timeline of critical vulnerabilities from late October through mid-November 2026, that window leaves businesses wide open to critical flaws for weeks at a time.

Here is how fast things moved over the last month.

21 October – Two major ecosystems expose critical flaws

Two critical flaws (rated 9.2 out of 10) were made public in PHP, the language behind WordPress, Craft CMS, and countless custom web applications. On the exact same day, a 9.2-rated flaw was fixed in the part of Node.js that unpacks compressed files. At this stage, patches were available, but the clock was officially ticking.

26–27 October – Less than a week to active attacks

Just five days after the PHP flaws went public, the US government’s cyber security agency (CISA) confirmed attackers were actively using them. A day later, on 27 October, the Node.js flaw made it onto the exact same exploited list, six days after its fix was released.

28 October – WordPress attacks start within hours

Attackers began probing the flaw within hours of the fix. Two days later, one security firm was blocking almost 63,000 attempts a day. CISA confirmed it as exploited on 3 November.

3 November – 12,000+ attacks in a single day

Six days after the WordPress fix went out, CISA added it to its list of actively exploited vulnerabilities. One security firm blocked more than 12,000 attempts to use the flaw in a single 24-hour window.

4 November – Rails image uploads put servers at risk

A flaw rated 9.8 out of 10 was published for Rails (Active Storage). For apps that accept image uploads, this vulnerability can let an attacker write files directly to the server and, in some instances, access critical information including passwords to other systems without needing to log in.

11 November – Six high-severity flaws hit Node.js

Node.js released another security update addressing six high-rated flaws (scoring up to 8.2) capable of crashing a server or leaking data straight from its memory. While no attacks have been reported yet, the window to patch before they start is shrinking.

12 November – Hours, not days, for IT provider tools

Attackers began breaking into servers used by managed service providers (MSPs) and IT teams to monitor, manage, and secure customer devices and networks remotely (specifically targeting N-able N-central). This happened within hours of a working attack being published.

Researchers found at least 21 servers taken over to mine cryptocurrency. Crucially, 19 of those compromised servers were already running the latest update. While no Australian examples have been named, a remote management tool like this acts as a direct pathway into every business it manages.

15 November – A 10/10 flaw hits WordPress plugins

A flaw rated 10 out of 10 for severity was published for Lazy Blocks, a WordPress plugin installed on more than 20,000 sites. It allows anyone to run their own code on the server without logging in. Security researchers expect active exploitation soon.

Meanwhile, across the same period, active attacks were already under way when Drupal announced a highly critical flaw in Drupal Commerce: a checkout system used by over 42,000 websites. Gravity Forms had a flaw rated 9.8 that could let an attacker run code without logging in, and Contact Form 7 had a high-rated flaw targeting file uploads. 

Why “up to date” isn’t the whole plan

The events of the past month highlight two realities for anyone running a website or web application:

  1. A week is now a long time. If your site is only updated every few months, it would have been exposed to applicable flaws for weeks.. Attackers don’t wait for your next scheduled maintenance window.
  2. Updates alone aren’t enough. Updates close the doors to risks everyone knows about. As the 12 November attack on fully updated servers proved, you also need active monitoring for flaws that don’t have a fix yet, and you need to know which outside tools can reach your systems.

What you can do right now

  • Check your third-party access: If you use an external IT provider, ask whether they run N-central and whether they were affected by the recent attack.
  • Shorten your update cycle: If your website or web application is only updated a few times a year, talk to us about Proactive Security & Maintenance. If you’re already on it, ask about moving to monthly updates.

Not sure when your website was last updated? Get in touch with your URL and we will let you know within a day, for free.