dbcve.org
Wise Paas\/rmmApplication · Advantech

CVE-2019-18227

HIGH · 7.5 CVSS v3.1 Published 2019-10-31
Fix available
A fix is available. Upgrade to after 3.3.29 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
Advantech WISE-PaaS/RMM, Versions 3.3.29 and prior. XXE vulnerabilities exist that may allow disclosure of sensitive data.

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 · moderate confidence

Advantech WISE-PaaS/RMM versions 3.3.29 and prior contain XML External Entity (XXE) injection vulnerabilities. The application parses XML input without properly disabling external entity processing, allowing attackers to craft malicious XML requests that can read local files, perform server-side request forgery, or cause denial of service.

MitigationDisable external entity processing and DTD parsing in all XML parsers used by the application, implement input validation and whitelisting for XML content, and consider using less complex data formats like JSON where possible.

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
Wise Paas\/rmmApplication
Affected:<= 3.3.29

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 if WISE-PaaS/RMM is installed
    Check for the application through installed services, running processes, or installation directories. Look for processes named 'WISE-PaaS', 'RMM', or related Advantech services on the system.
    Affected if The application is installed and running on the system
  2. Determine the installed version
    Locate version information in the application installation directory, typically in version files, about dialogs, or configuration files. Check the web interface or service information for the exact release version.
    Affected if The installed version is 3.3.29 or any prior version (3.3.29, 3.3.28, etc.)
  3. Identify XML processing functionality
    Examine the application for endpoints, modules, or functions that accept XML input. Look for XML parsers in the codebase, configuration files handling XML, or API endpoints accepting XML content types.
    Affected if The application processes XML input from users or external sources
  4. Check XML parser configuration for external entity settings
    Inspect XML parser initialization code and configuration to verify whether external entity processing and DTD parsing are explicitly disabled. Look for parser settings that control entity resolution and external references.
    Affected if External entity processing is enabled or not explicitly disabled in XML parser configurations

You are affected if WISE-PaaS/RMM version 3.3.29 or prior is installed AND the application processes XML input with external entity processing enabled.

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.

From vendor data
Upgrade available Upgrade to a release after 3.3.29
Interim mitigation

Disable external entity processing and DTD parsing in all XML parsers used by the application, implement input validation and whitelisting for XML content, and consider using less complex data formats like JSON where possible.

Fix this in Wise Paas\/rmm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
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,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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