← All posts

Website Security Australia: ASD’s 48-Hour Warning

Is Your Website Secure? Australia’s Cyber Agency Warns of 48-Hour Attacks

Australian businesses may have significantly less time to respond to security vulnerabilities than their existing website maintenance arrangements allow.

On 17 November 2026, the Australian Signals Directorate’s Australian Cyber Security Centre (ASD’s ACSC) issued a critical alert warning that attackers are exploiting software vulnerabilities at increasing speed.

The warning follows findings from ASD’s Annual Cyber Threat Report 2025–26, which recorded a 30% increase in publicly reported software vulnerabilities during the financial year.

More concerning, ASD reported that some vulnerabilities were successfully exploited within just 48 hours of patches or mitigation advice becoming available.

For organisations operating websites, membership portals, online payment systems and custom web applications, this raises an important question:

How quickly can your website provider identify and respond to a serious security vulnerability?

What has the Australian Government warned about?

ASD’s latest alert, Vulnerabilities are moving quickly, so patch, protect, prevent, highlights three developments:

  • Publicly reported software vulnerabilities increased by 30% in the 2025–26 financial year.
  • Some vulnerabilities were successfully exploited within 48 hours of patches or mitigation advice becoming available.
  • Automated and AI-enabled tools are helping attackers identify vulnerable systems and exploit them more quickly.

The warning is not about one particular vulnerability or software product.

It concerns a broader change in how quickly attackers can exploit weaknesses across internet-connected systems.

For businesses, the implication is straightforward: a security maintenance process that was adequate several years ago may no longer respond quickly enough to today’s threats.

Why this matters for Australian websites

Consider a typical business website running WordPress, Drupal or a custom application.

Behind the visible pages are multiple software components, potentially including:

  • The content management system and its plugins or extensions.
  • The programming language and application framework.
  • Web server software and supporting services.
  • Third-party integrations, APIs and authentication systems.
  • The operating system and hosting infrastructure.

Each component may have its own security updates and vulnerabilities.

When a serious vulnerability becomes public, attackers can begin identifying exposed systems using automated scanning tools.

In some cases, they may already be exploiting the vulnerability before the affected organisation becomes aware of it.

A website does not need to be particularly large or well known to be targeted. Automated attacks can search for vulnerable software across thousands of websites without selecting individual businesses in advance.

This creates a challenge for organisations whose website maintenance arrangements rely on monthly updates or occasional developer intervention.

The difference between website maintenance and security response

Many businesses pay for website maintenance without having a clear understanding of what happens when a critical vulnerability is disclosed.

A typical maintenance agreement might include plugin updates, backups, uptime monitoring and routine technical support.

Those services are useful, but they do not necessarily establish an emergency security response capability.

For example, consider a critical vulnerability disclosed on a Tuesday morning.

Who identifies whether your website uses the affected software?

Who determines whether the vulnerable feature is enabled?

Who decides whether the issue requires immediate attention?

Who applies the fix, and who checks that it has worked?

And if attackers were exploiting the vulnerability before the fix became available, who investigates whether your website was compromised?

These responsibilities need to be established before an incident occurs.

A maintenance schedule tells you when routine work happens. A security response process determines what happens when routine maintenance is no longer sufficient.

Why applying an update may not be enough

One of the most important distinctions in website security is the difference between fixing a vulnerability and investigating a possible compromise.

Installing a security update addresses the underlying software weakness.

It does not necessarily undo anything an attacker may have done while the vulnerability was present.

Depending on the vulnerability and the level of access obtained, an attacker could potentially have:

  • Created an unauthorised administrator account.
  • Modified application files.
  • Installed a malicious script or backdoor.
  • Accessed customer or member information.
  • Obtained credentials used by connected services.
  • Established another method of accessing the system.

Not every vulnerability results in these outcomes, and not every vulnerable website has been compromised.

However, where active exploitation has been confirmed and a website was exposed, remediation should consider whether investigation is required.

That may involve reviewing application and server logs, checking file integrity, examining administrator accounts and investigating unusual activity.

Simply reporting that the software is now up to date may not adequately address the risk.

What about websites managed by an MSP or external agency?

For organisations using a managed service provider, hosting company or digital agency, the question is often not whether someone is responsible for security.

It is where one provider’s responsibility ends and another’s begins.

An MSP might manage Microsoft 365, business networks, identity systems and DNS.

A hosting provider might maintain the underlying server infrastructure.

A website developer might maintain WordPress, PHP, plugins and custom application code.

These responsibilities can overlap, but they are not interchangeable.

For example, a fully patched hosting server does not guarantee that the WordPress installation or custom application running on it is secure.

Similarly, a WordPress plugin update does not address a vulnerability in the underlying PHP runtime or an insecure custom integration.

For associations and other organisations with multiple technology suppliers, this separation is particularly important.

When a critical vulnerability is disclosed, someone needs to coordinate the response across the relevant providers.

Without that coordination, each supplier may assume another party is handling the issue.

What does ASD recommend?

ASD’s November alert groups its recommendations into three areas: Patch, Protect and Prevent.

For website and application owners, these translate into practical operational questions.

1. Patch: Can critical vulnerabilities be addressed quickly?

Establish who monitors security advisories affecting your website and how critical updates are prioritised.

Confirm that your provider can respond outside the normal maintenance cycle when a serious vulnerability requires urgent action.

ASD’s Essential Eight maturity model includes a 48-hour remediation timeframe for critical vulnerabilities or those with working exploits in online services. This is a defined control requirement, not a guarantee that organisations have 48 hours before attackers act.

2. Protect: Is unnecessary exposure being reduced?

Review publicly accessible administrative interfaces, unused plugins, unsupported software and unnecessary services.

Apply appropriate access controls, including multifactor authentication, and restrict access to sensitive management functions.

Reducing the number of exposed components can reduce the opportunities available to attackers.

3. Prevent: Would you know if something went wrong?

Ensure that application and server logging is available and that suspicious activity can be investigated.

Confirm that backups are usable and that there is a process for checking website integrity following a security incident.

Where a patch cannot be applied immediately, determine whether temporary controls can reduce exposure until the underlying issue is resolved.

Five questions to ask your website provider

You do not need to be a technical specialist to establish whether your organisation has an appropriate security response process.

Start with these five questions:

  1. How do you identify new vulnerabilities affecting our website and its supporting software?
  2. How quickly can you respond when a critical vulnerability is disclosed or actively exploited?
  3. Who is responsible for security updates to the application, hosting environment and third-party integrations?
  4. If our website was vulnerable before a patch was applied, how would you determine whether it had been compromised?
  5. Can you provide evidence of recent security updates, monitoring and remediation work?

The answers should establish clear responsibilities, realistic response times and an auditable process.

Website security is becoming an operational responsibility

ASD’s warning reinforces an important change in how organisations need to approach website security.

A website is no longer simply a marketing asset that can be maintained periodically.

For many Australian businesses and associations, it is a production system supporting enquiries, payments, member services, customer information and business operations.

The consequences of a compromise can extend beyond the website itself.

A vulnerable application may expose personal information, interrupt essential services or provide access to connected systems.

The challenge is not to eliminate every vulnerability. No organisation can guarantee that.

It is to identify relevant vulnerabilities quickly, understand their consequences, reduce exposure and respond appropriately.

The question is no longer simply whether your website receives security updates. It’s whether your organisation can respond before a vulnerability becomes an incident.

How PIXELBIRD can help

PIXELBIRD works with Australian organisations, associations and managed service providers to investigate and resolve website and application security issues.

Our work includes reviewing WordPress and other content management systems, examining custom application code, identifying vulnerable components and investigating security incidents.

We also help organisations establish clearer responsibilities for ongoing website hosting, maintenance and technical support.

If you’re unsure who is responsible for the security of your website, or whether your current maintenance arrangements provide an appropriate response to critical vulnerabilities, a technical security review can help establish where the risks and responsibilities sit.

Explore PIXELBIRD’s Website Security & Privacy Audit


Source and further reading

Australian Signals Directorate, Australian Cyber Security Centre. Vulnerabilities are moving quickly, so patch, protect, prevent. Critical alert published 17 November 2026.

https://www.cyber.gov.au/alert/vulnerabilities-are-moving-quickly-so-patch-protect-prevent

Australian Signals Directorate. Essential Eight maturity model.

https://www.cyber.gov.au/publication/essential-eight-maturity-model