Saturday, 7 November 2026

SiteGuard WAF vulnerability lets attackers run commands as root

Attackers are abusing a command injection bug in SiteGuard Server Edition's statistics feature. Here is who is exposed, what the patch does, and why you should save evidence first.

Server rack with a highlighted patch note and glowing indicator in a data center.

The short version

  • CVE-2026-106931 is an OS command injection flaw in the statistics feature of SiteGuard Server Edition, which is on by default.
  • Exploitation can run commands as root on Linux or SYSTEM on Windows, and the vendor has confirmed real attacks.
  • Fixed builds are 8.00 Update 5 and, on FreeBSD, 7.00 Update 6; a file patch covers older versions.
  • CISA told US federal agencies to fix it by October 23 and added it to its exploited flaws list.
Quick read · 1 min

Attackers are exploiting CVE-2026-106931, a command injection bug in SiteGuard Server Edition, a Japanese web application firewall. The flaw sits in the statistics feature, which is on by default, and can let an attacker run commands as root or SYSTEM.

  • Affected: versions 2.20 and later before 8.00 Update 5, or before 7.00 Update 6 on FreeBSD.
  • The separate SiteGuard WordPress plugin is not the affected product.
  • US agencies were told to patch by October 23.

The vendor offers fixed releases and a file patch for older versions, and turning off statistics works as a stopgap. It warns that patching can erase attack traces, so admins should download the diagnostic information from the management screen first. The bug is rated as needing some prior access, so attackers likely chain it with stolen logins or another weakness. Who is behind the attacks is still unknown.

A tool that exists to block attacks on websites has become the way in. Attackers are exploiting a flaw in SiteGuard Server Edition, a Japanese web application firewall, that can let them run commands with the highest level of access on the server it is meant to protect.

Most people will never touch SiteGuard directly, but plenty of websites they use sit behind it. The vendor says its products protect more than 1.5 million websites. If a firewall like this is taken over, the attacker can change settings, plant files or read data on the web server itself. For site owners, admins and anyone who pays a hosting company to run their site, this is a patch-today problem, with one twist: you should save evidence before you fix it.

01

What the SiteGuard WAF vulnerability does

The SiteGuard WAF vulnerability, tracked as CVE-2026-106931, is an OS command injection bug. In plain terms, data that the software processes can be crafted so that it slips operating system commands through, and the server then runs them. A WAF, or web application firewall, is software that inspects traffic heading to a website and blocks attacks such as SQL injection or malicious scripts.

The weak spot is the statistics function, the part of SiteGuard that tallies detected attacks by type, source address and time. It is switched on by default. When the flaw is exploited, commands run as root on Linux and Unix systems or as SYSTEM on Windows, the most powerful accounts on each.

The developer, EG Secure Solutions, says abuse has already been confirmed. Japan’s CERT coordination center issued its own warning, and the bug carries a severity score of 8.5 under the current CVSS 4.0 scale (7.8 under the older version), which counts as high. Both the vendor and Japan’s vulnerability database labeled the alert urgent.

Hands at a workstation with a patch tool and dark hardware, screen blurred.
02

Which SiteGuard versions are affected

Only SiteGuard Server Edition installs that have the statistics function turned on are at risk. The affected releases are:

  • Apache httpd, Nginx and IIS (not FreeBSD): version 2.20 and later, before 8.00 Update 5.
  • Apache httpd and Nginx on FreeBSD: version 2.20 and later, before 7.00 Update 6.
  • Not affected: IIS editions from 3.10 through 4.00 Update 4.

One common mix-up is worth clearing up. There is also a popular WordPress security plugin called SiteGuard, but it is a separate product and is not the one covered by this warning. The vulnerable software is the server-side firewall that plugs into the web server.

03

How the attacks work, and what is still unknown

The vendor’s scoring describes the attack as local and requiring low privileges. That means the bug is not rated as something a stranger can trigger from anywhere on the internet with no foothold. The likely path is that an attacker first gets limited access to the server, through stolen credentials or another weakness, then uses the statistics flaw to jump to full control.

That is a description of what is possible, not a confirmed account of these attacks. Neither the vendor nor Japan’s CERT has said who is behind them, who was hit, how many systems were affected or what tools were used. The vendor told customers with direct support contracts about the problem in late September, before going public in mid-October.

The US government has taken notice too. The Cybersecurity and Infrastructure Security Agency added CVE-2026-106931 to its Known Exploited Vulnerabilities catalog, alongside the Plex2Shell bugs in Plex Media Server and a Siemens Software Center flaw, and told federal civilian agencies to fix it by October 23, 2026.

IT setup for incident response with forensic data and patch tools.
04

How to patch SiteGuard without losing the evidence

The order of steps matters here, because the vendor warns that applying the fix can wipe out traces of an attack. A sensible sequence looks like this:

  1. Check what you run. Confirm whether SiteGuard Server Edition is installed, which version it is and whether the statistics function is enabled. If a hosting firm or web agency runs your server, ask them directly.
  2. Save the diagnostic information. In the web management screen, open the diagnostic information page and download the file, then keep it somewhere safe.
  3. Update or patch. Move to 8.00 Update 5, or 7.00 Update 6 on FreeBSD. If you can’t upgrade, the vendor offers a patch that swaps out the files used in statistics processing, and it covers versions that are no longer supported.
  4. Use the stopgap if needed. If neither is possible right away, turning off the statistics function removes the exposed feature.
  5. Look for intrusion. Because the flaw is already being exploited, review the server for unexpected accounts, files and setting changes after patching.

If you suspect an attack is happening right now, don’t hold off on blocking it just to preserve evidence. Do both in parallel with whoever manages the server.

05

What this means if you run or use a website

For most readers, the risk is indirect. You won’t see a pop-up or a warning; the danger is that a site you trust, an online shop or a company portal, could be quietly taken over and used to steal data or serve malware. That is why the patch window matters more than the headline.

For small businesses, the useful takeaway is to know which security products sit on your server and who is responsible for updating them. A firewall that nobody patches can turn from shield into weak point.

The vendor’s fixed builds and patches are available now, and federal agencies were already past their October 23 deadline, so any SiteGuard server still on an older release should be treated as overdue.

06

Quick answers

What is CVE-2026-106931?

It is an OS command injection flaw in the statistics feature of SiteGuard Server Edition that can let an attacker run commands as root or SYSTEM. The vendor confirmed it is being exploited.

Is the SiteGuard WordPress plugin affected?

No. The WordPress plugin with the SiteGuard name is a different product. The warning covers SiteGuard Server Edition, the firewall that runs inside the web server.

How do I fix the SiteGuard flaw?

Download the diagnostic information first, then update to 8.00 Update 5 (or 7.00 Update 6 on FreeBSD) or apply the vendor’s file patch. Turning off the statistics function is a short-term workaround.

You're reading the quick version.