Who is affected
EG Secure Solutions SiteGuard Server Edition contains an OS command injection flaw that permits unauthenticated or low-privileged attackers to execute arbitrary commands with root or SYSTEM privileges. The record does not specify which versions are affected, the attack vector (local or remote), or whether authentication is required.
How to check whether this touches you
- Search your asset inventory for any installation of SiteGuard Server Edition, including test, staging, and development instances.
- If found, determine whether the instance is reachable over the network from untrusted sources or the internet; check firewall rules and network segmentation.
- Contact EG Secure Solutions or consult their security advisory to establish which versions of the product are vulnerable and whether your deployment matches that range.
- If you cannot obtain authoritative version information from the vendor, treat any SiteGuard Server Edition installation as potentially affected until you receive vendor guidance.
- Review access logs and authentication records for the past six months to identify who has interacted with the service.
What to do
- Immediately isolate any SiteGuard Server Edition instance from the internet and untrusted networks if a patch is not yet available or cannot be deployed within the CISA remediation window (23 October 2026).
- Apply the vendor's patch or mitigation as soon as it is released, prioritising internet-facing and production instances in accordance with BOD 26-04 guidance.
- If EG Secure Solutions provides no patch or mitigation, evaluate whether the product can be replaced or decommissioned; if neither is feasible, escalate to your risk management and compliance teams for a decision on continued use.
- Enable detailed command execution logging on the affected system and forward logs to your SIEM for continuous monitoring.
- Document the patch application date, method, and outcome for audit compliance.
If you find you were exposed
Assume exploitation could have occurred at any point since the vulnerability was introduced, as public disclosure often lags behind active abuse. Retrieve and preserve all system command history, authentication logs, and file access records from the affected instance covering at least the past six months, or the full retention period if shorter. Cross-reference any suspicious or unauthorised commands with your change management records to identify potential compromise. If you cannot retain logs beyond thirty days, prioritise forensic imaging of affected systems before log rotation overwrites evidence.