dbcve.org
Business Process ManagementApplication · Digiwin

CVE-2022-32458

HIGH · 7.5 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to 5.8.8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Digiwin BPM has a XML External Entity Injection (XXE) vulnerability due to insufficient validation for user input. An unauthenticated remote attacker can perform XML injection attack to access arbitrary system files.

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

Digiwin BPM processes XML input without proper validation, allowing attackers to inject malicious XML with external entity references. This XXE flaw enables unauthenticated remote attackers to read arbitrary system files by crafting XML that references local file paths through external entities.

MitigationDisable external entity processing and DTDs in all XML parsers used by the application. Implement strict input validation for XML payloads and consider using a security-focused XML parser that has XXE protections enabled by default.

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
Business Process ManagementApplication
Affected:< 5.8.8.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installed Digiwin BPM version
    Locate the Digiwin BPM installation directory and check the version information file, typically found in the application's about or system information page, or check the product version in the installed packages or registry depending on your deployment method
    Affected if The version is lower than 5.8.8.1 (any version < 5.8.8.1 is affected)
  2. Confirm XML processing is enabled
    Review the application configuration files and determine if the XML input processing feature is actively used by the BPM system for handling import, upload, or data exchange functions
    Affected if XML processing is enabled and the application accepts XML input from users or external sources
  3. Check XML parser configuration for external entity support
    Inspect the XML parser configuration files or settings within the Digiwin BPM application to determine whether external entity processing and DTD (Document Type Definition) parsing are permitted
    Affected if External entity processing and DTD parsing are not explicitly disabled in the XML parser configuration

Your environment is affected if Digiwin BPM version is below 5.8.8.1 AND the application has XML processing enabled with external entity support permitted in the parser configuration.

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 5.8.8.1 or later
Fixed in 5.8.8.1
Interim mitigation

Disable external entity processing and DTDs in all XML parsers used by the application. Implement strict input validation for XML payloads and consider using a security-focused XML parser that has XXE protections enabled by default.

Recommended fix Moderate confidence

Business Process Management 5.8.8.1 or later

  1. Verify current Digiwin BPM version by accessing the system administration panel or checking the installation
  2. Backup the current BPM database and configuration files before performing any upgrade
  3. Download the Business Process Management version 5.8.8.1 or later from the official Digiwin vendor portal
  4. Stop the BPM application services to ensure a clean upgrade process
  5. Install the new version following the vendor's standard upgrade documentation
  6. Restart the BPM services after successful installation
  7. Verify the system is operational and test XML processing functionality to confirm the XXE vulnerability is resolved
Caveat Review vendor release notes for any configuration or workflow changes between your current version and 5.8.8.1; test in non-production environment first

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

Fix this in Business Process Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32458 — 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-32458 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