VulnerabilityPublished 20 Mar 2026Updated 23 Mar 2026

CVE-2026-32666: Automated Logic WebCTRL Premium Server · CWE-290

Affects Automated Logic WebCTRL Premium ServerSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to v8.5 soon.

Data as of 1 Nov 2026, 11:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in v8.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Automated Logic WebCTRL Premium Server to v8.5.

Affected software

Product	Affected	Fixed in
Automated LogicWebCTRL Premium Server	Affected <8.5	Fixed in v8.5

AI-suggested

To mitigate CVE-2026-32666, organizations should implement strict network segmentation to isolate WebCTRL systems and BACnet traffic from untrusted networks and users. Deploying firewalls or access control lists (ACLs) to restrict BACnet protocol traffic only to authorized devices can reduce exposure. Network monitoring and anomaly detection should be enhanced to identify unusual BACnet packet patterns or spoofing attempts. Where possible, use VPNs or encrypted tunnels to protect BACnet communications over broader networks. Automated Logic or third-party vendors should be consulted for any available patches or firmware updates that add authentication or validation features. In the absence of patches, consider deploying compensating controls such as intrusion prevention systems (IPS) with BACnet protocol awareness. Regularly audit and review network access permissions and ensure that only trusted personnel have access to the building automation network. Finally, develop incident response plans specific to building automation system compromises to quickly detect and respond to exploitation attempts.

Description

WebCTRL systems that communicate over BACnet inherit the protocol's lack of network layer authentication. WebCTRL does not implement additional validation of BACnet traffic so an attacker with network access could spoof BACnet packets directed at either the WebCTRL server or associated AutomatedLogic controllers. Spoofed packets may be processed as legitimate.

Impact

The primary impact of this vulnerability is on the integrity of building automation systems managed by WebCTRL Premium Server. An attacker exploiting this flaw can send unauthorized commands to control HVAC, lighting, or other critical building functions, potentially causing operational disruptions, safety hazards, or damage to equipment. While confidentiality and availability are not directly impacted, the ability to manipulate system behavior can lead to indirect availability issues (e.g., disabling climate control in sensitive environments). Organizations relying on WebCTRL for critical infrastructure, commercial buildings, or industrial facilities face risks of unauthorized control, which could be leveraged for sabotage, espionage, or disruption. The ease of exploitation—requiring only network access without authentication—raises the threat level, especially in environments where network segmentation or access controls are weak. The lack of known exploits suggests the vulnerability is not yet widely weaponized, but the potential for damage is significant if exploited.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Mar 2026, 21:45 UTC

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats