Skip to content
Fencer Vulns
critical 9.8

CVE-2022-50981 json

Multiple Innomic VibroLine VLX HD 5.0 and avibia AVLX weak password requirements

published 2026-02-02 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-55958

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

An unauthenticated remote attacker can gain full access on the affected devices as they are shipped without a password by default and setting one is not enforced.

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
9 mo ago

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Innomic VibroLine VLX1 HD 5.0
  • Innomic VibroLine VLX2 HD 5.0
  • Innomic VibroLine VLX4 HD 5.0
  • Innomic VibroLine VLX6 HD 5.0
  • Innomic VibroLine VLX8 HD 5.0
  • avibia AvibiaLine AVLX1 HD 5.0
  • avibia AvibiaLine AVLX2 HD 5.0
  • avibia AvibiaLine AVLX4 HD 5.0
  • avibia AvibiaLine AVLX6 HD 5.0
  • avibia AvibiaLine AVLX8 HD 5.0
  • Innomic VibroLine VLE1 HD 5.0
  • Innomic VibroLine VLE2 HD 5.0
  • Innomic VibroLine VLE4 HD 5.0
  • Innomic VibroLine VLE6 HD 5.0
  • Innomic VibroLine VLE8 HD 5.0
  • avibia AvibiaLine AVLE1 HD 5.0
  • avibia AvibiaLine AVLE2 HD 5.0
  • avibia AvibiaLine AVLE4 HD 5.0
  • avibia AvibiaLine AVLE6 HD 5.0
  • avibia AvibiaLine AVLE8 HD 5.0
  • Innomic VibroLine VLE1 HD 4.0
  • Innomic VibroLine VLE2 HD 4.0
  • Innomic VibroLine VLE4 HD 4.0
  • Innomic VibroLine VLE6 HD 4.0
  • Innomic VibroLine VLE8 HD 4.0
  • Innomic VibroLine VLX1 HD 4.0
  • Innomic VibroLine VLX2 HD 4.0
  • Innomic VibroLine VLX4 HD 4.0
  • Innomic VibroLine VLX6 HD 4.0
  • Innomic VibroLine VLX8 HD 4.0

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.