Key Takeaways
- The Australian Cyber Security Centre (ACSC) has issued an alert about a worldwide exploitation campaign that targets vulnerabilities in popular content‑management systems (CMS) and their plugins.
- Many small‑ to medium‑sized Australian businesses have already been compromised, with attackers deploying webshells that give them persistent, stealthy access to victim sites.
- The campaign leverages a long list of known CVEs affecting WordPress, Craft CMS, MaxSite CMS, MetInfo CMS, and Joomla JCE, ranging from 2020‑era flaws to newly disclosed 2025‑2026 vulnerabilities.
- ACSC warns that artificial‑intelligence‑assisted tools may be helping threat actors scan, identify, and exploit these weaknesses at unprecedented speed and scale.
- Immediate defensive actions include applying the latest patches, removing unused themes/plugins, hardening file‑system permissions, monitoring for unauthorized file creation, and restricting privileged processes on web servers.
- Organizations should treat this alert as a reminder that CMS ecosystems remain a high‑value target; continuous patch management, configuration hardening, and proactive threat‑hunting are essential to reduce risk.
Overview of the ACSC Alert
The Australian Cyber Security Centre (ACSC) released a security advisory detailing a large‑scale, global exploitation campaign that is actively scanning and compromising websites running vulnerable content‑management systems and associated plugins. The alert emphasizes that the threat is not limited to a single geographic region; rather, attackers are casting a wide net across the internet, seeking any exposed CMS instance that contains known, unpatched flaws. While the campaign is international, the ACSC specifically notes that numerous Australian organizations—particularly small‑ to medium‑sized enterprises—have already fallen victim to the activity. The advisory serves both as a warning of ongoing compromise and as a call to action for administrators to harden their web environments before further damage occurs.
Impact on Australian Businesses and the Role of Webshells
According to the ACSC, many Australian businesses have already been affected by the malicious activity, with the primary post‑exploitation tactic being the deployment of webshells on compromised sites. A webshell is a malicious script uploaded to a web server that provides the attacker with remote, persistent command‑line access to the underlying system. Once a webshell is in place, threat actors can execute a variety of harmful actions: they can disrupt website availability, exfiltrate sensitive data such as customer credentials or payment information, install additional malware (including ransomware or cryptominers), and use the compromised host as a pivot point to move laterally within the victim’s internal network. Because webshells often blend in with legitimate files and can be triggered via ordinary HTTP requests, they are notoriously difficult to detect without rigorous file‑integrity monitoring and behavioural analysis.
Technical Details – Exploited CMS Platforms and Plugins
The ACSC’s advisory enumerates a substantial list of vulnerabilities that are being abused in this campaign. The affected products span several widely used CMS platforms and numerous WordPress plugins, illustrating the breadth of the attack surface. Notable examples include:
- WordPress plugins: Simple File List (CVE‑2025-34085 / CVE‑2020-36847), WavePlayer (CVE‑2025-12057), BerqWP (CVE‑2025-7443), WPBookit (CVE‑2025-7852), Ninja Forms (CVE‑2026-0740), ThemeREX Addons (CVE‑2026-1969), Breeze Cache (CVE‑2026-3844), pay‑uz (CVE‑2026-31843), ACF Extended (CVE‑2025-13486), WPvivid Backup (CVE‑2026-1357), Gravity Forms (CVE‑2025-12352), and GutenKit/Hunk Companion (likely CVE‑2024-9234).
- Craft CMS: CVE‑2025-32432
- MaxSite CMS: CVE‑2026-3395
- MetInfo CMS: CVE‑2026-29014
- Joomla JCE: CVE‑2026-48907
Many of these flaws involve improper input validation, insecure file‑upload mechanisms, or inadequate access controls that allow unauthenticated or low‑privileged users to execute arbitrary code or upload malicious files. The diversity of the targeted components underscores that attackers are not relying on a single zero‑day; instead, they are chaining together known, often‑older vulnerabilities that remain unpatched in many deployments.
Potential AI Assistance in the Campaign
The ACSC highlights a concerning trend: the campaign may be augmented by artificial‑intelligence‑driven tools that accelerate the discovery and exploitation of vulnerable CMS instances. AI‑enhanced scanners can rapidly crawl the internet, fingerprint CMS versions and plugin installations with greater accuracy than traditional signature‑based methods, and prioritize targets based on the likelihood of successful exploitation. Furthermore, machine‑learning models can help automate the generation of evasive payloads that bypass basic web‑application firewalls (WAFs) or intrusion‑detection signatures. While the advisory does not provide concrete evidence of AI use, the warning serves as a reminder that adversaries are increasingly leveraging automation and advanced analytics to scale their operations, making timely patching and proactive monitoring even more critical.
Recommended Mitigation Steps
To defend against this ongoing threat, the ACSC prescribes a set of practical, prioritized actions for website administrators and security teams:
- Apply patches immediately – Ensure that all CMS cores, themes, and plugins are updated to the latest versions that address the listed CVEs. Enable automatic updates wherever the platform supports them.
- Remove unnecessary components – Deactivate and delete any plugins, themes, or extensions that are not actively used, as each additional component expands the attack surface.
- Harden file‑system permissions – Configure web directories to be read‑only where possible, limiting the ability of attackers to write webshells or other malicious files.
- Monitor for unauthorized file creation – Deploy file‑integrity monitoring (FIM) or web‑application security solutions that alert on new or modified files within the web root, especially those with executable extensions (.php, .py, .pl, etc.).
- Restrict access to sensitive directories – Use web‑server configuration (e.g., Apache
.htaccessor Nginxlocationblocks) to deny direct access to directories such aswp-content/uploads,plugins, orthemesunless absolutely required. - Control process execution – Implement policies that prevent the web‑server user from spawning unexpected child processes (e.g., via
exec,system, orshell_execfunctions) and consider using containerization or sandboxing to isolate web workloads. - Conduct regular vulnerability scans – Utilize reputable scanning tools to identify missing patches, misconfigurations, or known vulnerable versions before attackers do.
- Review logs and enable alerting – Ensure that web‑server, application, and security‑device logs are retained and monitored for indicators of compromise such as suspicious POST requests, unfamiliar user‑agent strings, or anomalous outbound connections.
Broader Implications and Conclusion
The ACSC alert underscores a persistent reality: content‑management systems, despite their ease of use and widespread adoption, remain a favored entry point for cyber‑criminals due to the sheer volume of deployments and the frequent lag in applying updates. The exploitation of multiple, well‑known vulnerabilities across different platforms indicates that attackers are opportunistic, leveraging any unpatched flaw they can find rather than waiting for a novel zero‑day. The possible involvement of AI‑assisted reconnaissance further amplifies the speed at which these threats can proliferate, meaning that organizations must shift from reactive patch cycles to continuous vulnerability management.
For Australian businesses—and indeed any organization that relies on a CMS—the advisory is a timely reminder to inventory all web‑facing assets, validate that each component is current and necessary, and implement layered defenses that limit the impact of a successful breach. By combining prompt patching, strict file‑system controls, vigilant monitoring, and proactive threat‑hunting, organizations can significantly reduce the likelihood that a webshell will take hold and that attackers will gain a foothold for deeper network intrusion. In an era where automated, AI‑enhanced attacks are becoming the norm, maintaining basic cyber‑hygiene is not just advisable; it is essential for preserving the integrity, availability, and confidentiality of online services.

