CyberSecBulletin
CVE-2025-47809NVD status: Deferred

CodeMeter: Least Privilege Violation

Published Updated By the CyberSecBulletin desk

CVE-2025-47809 is a high-severity least privilege violation vulnerability in CodeMeter from Wibu, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. The record lists version 8.30a as the first without the flaw, so updating CodeMeter to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update CodeMeter to 8.30a or a later version.
  2. Update Desigo CC family V8 to V8.0 QU2 or a later version.
  3. Update SENTRON Powermanager V8 to V8.0 QU2 or a later version.
  4. Read the advisory on wibu.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
WibuCodeMeterbefore 8.30a8.30a
SiemensDesigo CC family V5.0all versionsNot stated
SiemensDesigo CC family V5.1all versionsNot stated
SiemensDesigo CC family V6all versionsNot stated
SiemensDesigo CC family V7all versionsNot stated
SiemensDesigo CC family V8before V8.0 QU2V8.0 QU2
SiemensSENTRON Powermanager V5all versionsNot stated
SiemensSENTRON Powermanager V6all versionsNot stated
SiemensSENTRON Powermanager V7all versionsNot stated
SiemensSENTRON Powermanager V8before V8.0 QU2V8.0 QU2
SiemensSIMATIC PDM Maintenance Station V5.0before V5.0 SP2V5.0 SP2
SiemensSIMATIC WinCC OA V3.18before V3.18 P032V3.18 P032
SiemensSIMATIC WinCC OA V3.19before V3.19 P020V3.19 P020
SiemensSIMATIC WinCC OA V3.20before V3.20 P008V3.20 P008

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (mitre.org).

Official description

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 CodeMeter Control Center component must not have been restarted. In this scenario, the local user can navigate from Import License to a privileged instance of Windows Explorer.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Least Privilege Violation

The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.

How developers prevent this class of flaw

  • Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

More Least Privilege Violation vulnerabilities (CWE-272)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Least Privilege Violation vulnerabilities

Spotted an error? Tell us.