Skip to content

Product

wibu codemeter vulnerabilities

10 published CVES affecting wibu codemeter, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
10
Critical
3
High
6
Medium
1
Low
0
Unscored
0
CISA KEV
0

Latest wibu codemeter CVEs

Newest publication first

  1. HighCVSS 8.2 EPSS 0.18%

    Wibu CodeMeter before 8.30a sometimes allows privilege escalation immediately after installation (before a logoff or reboot). For exploitation, there must have been an unprivileged installation with UAC, and the CodeMeter Control Center component must be installed, and the CodeMe...

  2. HighCVSS 7.5 EPSS 0.84%

    CodeMeter (All versions prior to 6.90 when using CmActLicense update files with CmActLicense Firm Code) has an issue in the license-file signature checking mechanism, which allows attackers to build arbitrary license files, including forging a valid license file as if it were a v...

  3. HighCVSS 7.5 EPSS 0.64%

    This vulnerability allows an attacker to use the internal WebSockets API for CodeMeter (All versions prior to 7.00 are affected, including Version 7.0 or newer with the affected WebSockets API still enabled. This is especially relevant for systems or devices where a web browser i...

  4. CriticalCVSS 9.8 EPSS 0.68%

    Protocol encryption can be easily broken for CodeMeter (All versions prior to 6.90 are affected, including Version 6.90 or newer only if CodeMeter Runtime is running as server) and the server accepts external connections, which may allow an attacker to remotely communicate with t...

  5. CriticalCVSS 9.8 EPSS 2.1%

    Multiple memory corruption vulnerabilities exist in CodeMeter (All versions prior to 7.10) where the packet parser mechanism does not verify length fields. An attacker could send specially crafted packets to exploit these vulnerabilities.

  6. MediumCVSS 5.4 EPSS 3.9%

    Cross-site scripting (XSS) vulnerability in the "advanced settings - time server" module in Wibu-Systems CodeMeter before 6.50b allows remote attackers to inject arbitrary web script or HTML via the "server name" field in actions/ChangeConfiguration.html.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.