Skip to content
Fencer Vulns
high 7.5

CVE-2021-41545 json

A vulnerability has been identified in Desigo DXR2 (All versions < V01.21.142.5-22), Desigo PXC3 (All versions < V01.21.142.4-18), Desigo P…

published 2022-05-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-28563

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

A vulnerability has been identified in Desigo DXR2 (All versions < V01.21.142.5-22), Desigo PXC3 (All versions < V01.21.142.4-18), Desigo PXC4 (All versions < V02.20.142.10-10884), Desigo PXC5 (All versions < V02.20.142.10-10884). When the controller receives a specific BACnet protocol packet, an exception causes the BACnet communication function to go into a “out of work” state and could result in the controller going into a “factory reset” state.

Patch / fix

  • siemens desigo_dxr2_firmware 01.21.142.5-22
  • siemens desigo_pxc3_firmware 01.21.142.4-18
  • siemens desigo_pxc4_firmware 02.20.142.10-10884
  • siemens desigo_pxc5_firmware 02.20.142.10-10884

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-132-10 updated cvss 7.5

Siemens Desigo PXC and DXR Devices

  • Siemens Desigo DXR2 < 01.21.142.5-22
    affected: fixed in v01.21.142.5-22 siemens.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • Siemens Desigo DXR2
  • Siemens Desigo PXC3
  • Siemens Desigo PXC4
  • Siemens Desigo PXC5

Classification

Weakness

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.