CVE-2026-22543: EFACEC QC 60/90/120 · Week encoding for passwords
Affects EFACEC QC 60/90/120Source CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EFACECQC 60/90/120 | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict network access to the EFACEC QC device web interfaces by implementing strict network segmentation and firewall rules to limit access to trusted management networks only. 2. Deploy VPNs or encrypted tunnels (e.g., IPsec, TLS) for all management traffic to ensure credentials are not transmitted in cleartext or easily reversible encoding. 3. Verify and enforce the use of HTTPS with valid certificates on the device web server to protect credentials in transit. 4. Implement strong authentication mechanisms such as multi-factor authentication (MFA) if supported by the device or through external authentication proxies. 5. Regularly monitor network traffic for suspicious activities, including repeated failed login attempts or unusual access patterns to the device management interface. 6. Engage with EFACEC for firmware updates or patches that address this vulnerability and plan for timely deployment once available. 7. Conduct security awareness training for network administrators to recognize the risks of weak credential transmission and enforce best practices. 8. Consider deploying network intrusion detection/prevention systems (IDS/IPS) to detect attempts to intercept or exploit this vulnerability.
Description
The credentials required to access the device's web server are sent in base64 within the HTTP headers. Since base64 is not considered a strong cipher, an attacker could intercept the web request handling the login and obtain the credentials