LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22543: WEEK ENCODING FOR PASSWORDS

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

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22543 affects EFACEC QC 60/90/120 version 8. Login credentials for the device web server are sent as base64 in HTTP headers. Base64 is encoding, not encryption, so someone able to intercept the relevant web traffic could recover credentials.

Executive priority

Treat as a medium-priority confidentiality risk for environments using affected EFACEC devices. Prioritize sites where management traffic crosses shared, remote, or weakly controlled networks. There is no source-confirmed active exploitation, but credential exposure could enable unauthorized device access.

Technical view

The CVE describes weak password encoding, mapped to CWE-261. The record scores it CVSS 4.0 6.9, with adjacent attack vector, low complexity, low privileges, no user interaction, and high confidentiality impact. The listed affected product is EFACEC QC 60/90/120 version 8; default status is otherwise unaffected.

Likely exposure

Exposure is most relevant where the device web management interface is reachable over networks an attacker can observe or access. The CVSS vector indicates adjacent-network scope and low privileges. The source bundle does not identify internet-wide exposure or additional affected versions.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. Practical risk depends on whether an attacker can intercept the login request to the device web server. No public exploit details are included in the source bundle.

Researcher notes

Evidence is limited to the CVE record and referenced Thales page. No patch, workaround, firmware version, or advisory detail is provided in the bundle. Validate only in authorized environments and avoid publishing credential-capture procedures.

Mitigation direction

  • Check EFACEC or referenced vendor guidance for a confirmed fix or configuration change.
  • Limit access to the device web management interface to trusted administrative networks.
  • Avoid using the web login over untrusted or shared network paths.
  • Rotate device web credentials if interception is suspected.

Validation and detection

  • Inventory EFACEC QC 60/90/120 devices and confirm version 8 presence.
  • Confirm whether the device web server login sends credentials in base64 headers.
  • Review network placement for paths where management traffic could be intercepted.
  • Check vendor advisories for updated affected-version and remediation details.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-261: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22543 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-22543Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EFACECQC 60/90/1208unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-261 · source CWE mapping

Weak Encoding for Password

Weak Encoding for Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.