CVE-2026-130596 in FusionPBX
Summary
by MITRE • 11/17/2026
FusionPBX through 5.6.5 contains a path traversal vulnerability in app/fax/fax_emails.php that allows unauthenticated remote attackers to write files by using a crafted MIME attachment filename. Attackers can email the polled fax mailbox with a spoofed authorized From address and use ../ sequences in the filename to create or overwrite web-server-writable files with .pdf/.tif content.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
The vulnerability identified in FusionPBX versions through 5.6.5 represents a critical path traversal flaw located within the fax processing module, specifically in the file app/fax/fax_emails.php. This security defect allows unauthenticated remote attackers to execute arbitrary file writes on the underlying server infrastructure by manipulating MIME attachment filenames during the email ingestion process. The core technical failure stems from insufficient validation and sanitization of user-supplied input derived from email headers and attachments before they are processed for storage or display. When an email containing a fax attachment is received, the application extracts the filename associated with that attachment to determine where to save the resulting document file on the disk. However, the system fails to adequately strip directory traversal sequences such as ../ from this filename string. Consequently, if an attacker crafts an email with a specially constructed MIME attachment filename containing these relative path indicators, the operating system interprets them not as literal characters but as instructions to navigate up the directory hierarchy and write files into arbitrary locations accessible by the web server process user account.
The operational impact of this vulnerability is severe because it effectively grants remote code execution capabilities under specific conditions. By leveraging the ability to overwrite or create new files in directories writable by the web server, an attacker can place malicious scripts such as PHP shells within a publicly accessible directory like /var/www/html/fusionpbx/app/fax/attachments/. Since FusionPBX is typically deployed behind firewalls and often requires authentication for administrative access, this vulnerability provides a mechanism to bypass those controls entirely. The requirement that the email must appear to come from an authorized From address adds a layer of complexity but does not mitigate the risk significantly if social engineering or spoofing techniques are employed, especially in environments where SPF/DKIM/DMARC records may be misconfigured or ignored by internal mail relays. Once a web shell is successfully written and placed in a location that can be accessed via HTTP requests, the attacker gains full control over the server environment running under the privileges of the web service account, which often includes read/write access to database files and configuration settings.
From an industry standards perspective, this vulnerability aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal or directory traversal. The exploitation technique involves manipulating input that is used to construct file paths without proper neutralization of special elements. Furthermore, the attack vector maps directly to MITRE ATT&CK techniques related to Initial Access and Execution. Specifically, it relates to T1505.003: Server Software Component: Web Shell, where attackers deploy web shells as a persistent backdoor mechanism after gaining initial foothold through input manipulation vulnerabilities like this one. The fact that the attack is remote and unauthenticated classifies it under high-severity threat profiles requiring immediate remediation due to its potential for complete system compromise without any prior authentication credentials.
Mitigation strategies must focus on both immediate patching and long-term architectural improvements. The primary defense is to upgrade FusionPBX to a version later than 5.6.5 where this specific input validation flaw has been addressed by the developers. In cases where upgrading is not immediately feasible, administrators should implement strict web application firewall rules that detect and block HTTP requests containing path traversal sequences such as ../ or ..\ in query parameters or file upload fields. Additionally, reinforcing email authentication protocols like SPF, DKIM, and DMARC can reduce the likelihood of successful spoofing attacks used to trigger this vulnerability. It is also recommended to configure the web server process with minimal privileges, ensuring that even if a file write occurs, it cannot overwrite critical system binaries or access sensitive configuration files outside designated directories. Regular auditing of uploaded content in public-facing directories and implementing strict allow-lists for permitted filename characters can further reduce the attack surface associated with this class of vulnerabilities.