Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100389 Overview
CVE-2026-100389 is a remote code execution vulnerability in GestSup, an open-source helpdesk and ticketing application. Versions prior to 3.2.62 fail to enforce blocked file extension filtering within the basic Internet Message Access Protocol (IMAP) connector's attachment handler. Unauthenticated attackers can email PHP attachments to a monitored mailbox, and the application writes those files into the web-accessible upload/ticket directory. Requesting the uploaded file through the web server executes attacker-controlled PHP code. The flaw is classified as CWE-434: Unrestricted Upload of File with Dangerous Type.
Critical Impact
Unauthenticated attackers can achieve remote code execution on the GestSup web server by sending a crafted email with a PHP attachment.
Affected Products
- GestSup versions prior to 3.2.62
- GestSup instances configured with the basic IMAP connector for ticket ingestion
- Deployments where the upload/ticket directory is served by the web server with PHP execution enabled
Discovery Timeline
- 2026-09-25 - CVE-2026-100389 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-100389
Vulnerability Analysis
GestSup supports ticket creation by polling a mailbox over IMAP and converting incoming email into tickets. The basic IMAP connector extracts attachments from each message and stores them in the upload/ticket directory so agents can review them from the ticket interface. The attachment handler does not consult the application's blocked file extension list that governs normal web uploads. An attacker who knows or discovers a monitored mailbox address can send an email with a .php attachment and have the file written verbatim to a location the web server executes. Because upload/ticket is reachable over HTTP and PHP is handled by the server, retrieving the file triggers code execution in the GestSup application context. See the VulnCheck advisory and the Spiizn technical write-up for a complete walk-through.
Root Cause
The IMAP attachment code path bypasses the extension deny list enforced on standard HTTP uploads. The attachment is persisted using its original filename inside a directory served by the web server, with no rename, content inspection, or server-side execution restriction.
Attack Vector
Exploitation requires only the ability to send an email to a mailbox GestSup monitors. No authentication, user interaction, or prior access to the GestSup web interface is needed. After the ticket is created, the attacker requests the attachment URL and the PHP interpreter executes the payload. Technical reproduction steps are documented in the Spiizn blog post.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-100389
Indicators of Compromise
- Files with executable extensions such as .php, .phtml, or .phar present inside the upload/ticket directory
- Inbound emails to monitored mailboxes with attachments whose extensions are not typical office or image formats
- Web server access logs showing GET requests directly to files under /upload/ticket/ followed by outbound connections from the PHP process
- New or modified tickets created from external email addresses that reference unusual attachment filenames
Detection Strategies
- Alert on process creation by the PHP-FPM or web server user that spawns shells, curl, wget, or interpreters such as python or perl
- Monitor file creation events in the GestSup upload/ticket directory and flag any filename ending in a server-executable extension
- Correlate IMAP mailbox events with filesystem writes and subsequent HTTP requests to the written path
Monitoring Recommendations
- Enable verbose web server access logging for the GestSup virtual host and retain logs for incident review
- Forward endpoint, web, and mail telemetry into a central analytics platform to correlate email ingestion, file writes, and HTTP execution
- Track outbound network connections initiated by the GestSup web server process, which should be limited under normal operation
How to Mitigate CVE-2026-100389
Immediate Actions Required
- Upgrade GestSup to version 3.2.62 or later using the official download page
- Audit the upload/ticket directory for any file with a server-executable extension and remove suspicious artifacts
- Review recently created tickets originating from email to identify abuse of the IMAP connector
- Rotate credentials and secrets accessible to the GestSup application if evidence of execution is found
Patch Information
The vendor addressed the vulnerability in GestSup 3.2.62. Release notes are published on the GestSup changelog. The fix extends the blocked extension check to attachments ingested through the IMAP connector.
Workarounds
- Disable the basic IMAP connector until the patched version is deployed
- Configure the web server to deny execution of PHP within upload/ticket, for example using an Apache <Directory> block or an Nginx location rule that disables the PHP handler
- Restrict the monitored mailbox so only trusted senders can submit tickets, using mail gateway rules or an allow list
- Place the upload/ tree outside the document root and serve attachments through an authenticated download handler
# Nginx example: disable PHP execution inside the GestSup upload/ticket directory
location ^~ /upload/ticket/ {
location ~ \.(php|phtml|phar)$ {
deny all;
return 403;
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

