CVE-2019-13551
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 · uneditedAdvantech WISE-PaaS/RMM, Versions 3.3.29 and prior. Path traversal vulnerabilities are caused by a lack of proper validation of a user-supplied path prior to use in file operations. An attacker can leverage these vulnerabilities to remotely execute code while posing as an administrator.
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 confidencePath traversal vulnerability in Advantech WISE-PaaS/RMM versions 3.3.29 and prior allows remote attackers to execute code by manipulating user-supplied paths used in file operations without proper validation, enabling them to pose as administrator.
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<= 3.3.29CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify WISE-PaaS/RMM installed versionCheck the application version through the RMM management console, installer information, or service metadata. The version is typically displayed in the dashboard or about section of the web interface, or can be found in the installation directory's version file.Affected if The installed version is 3.3.29 or any version prior to 3.3.29 (e.g., 3.3.28, 3.3.0, 3.2.x).
-
Verify web management interface exposureDetermine if the WISE-PaaS/RMM web interface (typically on ports 8080, 443, or 80) is accessible from untrusted networks or the internet. Check network firewall rules and reverse proxy configurations.Affected if The RMM web interface is exposed to untrusted networks without proper network segmentation or authentication barriers.
-
Check for unauthorized administrator accountsReview the user management section of the RMM console for any unfamiliar administrator accounts or accounts created without authorization, especially those with unusual names or recent creation timestamps.Affected if Unexpected administrator accounts exist in the system that were not created by legitimate administrators.
-
Inspect RMM server logs for path traversal attemptsSearch RMM server logs for patterns indicating path traversal attempts, such as sequences containing '../' or '..\' in file operation requests, particularly in endpoints related to file upload, download, or backup functionality.Affected if Log entries show '..' traversal sequences in request parameters, especially in file operation endpoints.
-
Review file operation logs for suspicious activityExamine audit logs for file read/write operations that accessed system directories outside the expected RMM data folders, looking for access to configuration, system, or parent directories.Affected if File operations have accessed paths outside the designated RMM application directory, such as Windows\System32 or /etc/.
You are affected if the installed WISE-PaaS/RMM version is 3.3.29 or lower and the system is accessible over the network where an attacker could send manipulated path parameters to file operation endpoints.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade WISE-PaaS/RMM to a version newer than 3.3.29; implement strict path validation and sanitization to ensure user-supplied paths cannot escape intended directories.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13551 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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