dbcve.org
Desigo Pxc5 FirmwareOperating system · Siemens

CVE-2022-24039

CRITICAL · 9.0 CVSS v3.1 Published 2022-05-10
Fix available
A fix is available. Upgrade to 02.20.142.10-10884 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Desigo PXC4 (All versions < V02.20.142.10-10884), Desigo PXC5 (All versions < V02.20.142.10-10884). The “addCell” JavaScript function fails to properly sanitize user-controllable input before including it into the generated XML body of the XLS report document, such that it is possible to inject arbitrary content (e.g., XML tags) into the generated file. An attacker with restricted privileges, by poisoning any of the content used to generate XLS reports, could be able to leverage the application to deliver malicious files against higher-privileged users and obtain Remote Code Execution (RCE) against the administrator’s workstation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The 'addCell' JavaScript function in Desigo PXC4 and PXC5 fails to sanitize user input before embedding it into the XML body of generated XLS reports, allowing XML injection. An attacker with restricted privileges can poison report content to deliver malicious files to higher-privileged users, achieving RCE on the administrator's workstation.

MitigationUpgrade Desigo PXC4/PXC5 to version V02.20.142.10-10884 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Desigo Pxc5 FirmwareOperating system
Affected:< 02.20.142.10-10884
Desigo Pxc4 FirmwareOperating system
Affected:< 02.20.142.10-10884

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the Desigo device and confirm it is either a PXC4 or PXC5 controller by checking the model label or system information in the web interface or device documentation
    Affected if The device is a PXC4 or PXC5 controller
  2. Check installed firmware version
    Access the device web interface or CLI and navigate to the system information or firmware version section to determine the current firmware build number
    Affected if The firmware version is earlier than 02.20.142.10-10884 (for example, 02.20.xxx or earlier builds)
  3. Verify XLS report generation is accessible
    Check if the report generation feature that produces XLS reports is enabled and accessible to users in the system configuration or user management settings
    Affected if XLS report generation feature is enabled and accessible to users
  4. Check user privilege configuration
    Review user accounts and their assigned privilege levels to determine if restricted or low-privilege users have access to the report generation functionality
    Affected if Restricted or low-privilege user accounts can access or generate XLS reports

The environment is affected if the device is a PXC4 or PXC5 running firmware version earlier than 02.20.142.10-10884 AND the XLS report generation feature is accessible to users with restricted privileges, allowing them to inject malicious content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 02.20.142.10-10884 or later
Fixed in 02.20.142.10-10884
Interim mitigation

Upgrade Desigo PXC4/PXC5 to version V02.20.142.10-10884 or later to remediate this vulnerability.

Recommended fix High confidence

Desigo PXC4/PXC5 Firmware V02.20.142.10-10884 or later

  1. Identify the specific Desigo PXC4 or PXC5 device model and current firmware version
  2. Download the firmware version 02.20.142.10-10884 or later from Siemens cert-portal.siemens.com
  3. Follow Siemens firmware update instructions for the specific device (typically via the device web interface or management tool)
  4. Verify the firmware upgrade was successful by checking the installed version
  5. Confirm the 'addCell' function now properly sanitizes input before including it in XLS report XML
Caveat Review Siemens release notes for any configuration or compatibility changes between your current version and V02.20.142.10-10884

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Desigo Pxc5 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24039 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24039 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data