Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2019-19731: Path Traversal and Arbitrary File Write in Roxy Fileman 1.4.5 for .NET

Published Dec 16, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS11.6%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Roxyfileman
IdentifiersCVE-2019-19731CWE-22 · Improper Limitation of a Pathname…

Roxy Fileman 1.4.5 for .NET contains a path traversal vulnerability in the RENAMEFILE action, allowing remote attackers to write uploaded files to arbitrary locations on the server. The vulnerability arises due to insufficient validation of file paths and an incomplete blacklist of file extensions, permitting the upload and placement of Windows shortcut (.lnk) files into sensitive directories such as the Startup folder. This can be exploited to achieve remote code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to upload and place malicious files, such as Windows shortcut files, into arbitrary locations on the server, including the Startup folder. This can lead to remote code execution with the privileges of the affected user or service, potentially resulting in full system compromise.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, restrict access to the RENAMEFILE action to trusted users only, implement strict input validation and output encoding, and use a whitelist approach for allowed file extensions. Monitor and audit file uploads and server directories for unauthorized files, especially in sensitive locations such as the Startup folder.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of Roxy Fileman that properly validates file paths and implements a comprehensive whitelist of allowed file extensions. Ensure that user-supplied paths are sanitized to prevent directory traversal, and restrict file uploads to safe directories only.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
RoxyfilemanRoxy Filemanapplication
FAQ

Frequently asked questions

Is CVE-2019-19731 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-19731 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-19731?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-19731.
Is there a patch for CVE-2019-19731?
Upgrade to a patched version of Roxy Fileman that properly validates file paths and implements a comprehensive whitelist of allowed file extensions. Ensure that user-supplied paths are sanitized to prevent directory traversal, and restrict file uploads to safe directories only.
What products are affected by CVE-2019-19731?
Roxyfileman Roxy Fileman.
How severe is CVE-2019-19731?
CVE-2019-19731 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 11.6% (96th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.