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-102374 Overview
CVE-2026-102374 is a stored cross-site scripting vulnerability [CWE-79] in GestSup versions before 3.2.62. The flaw resides in the IMAP OAuth connector, which double-decodes MIME-encoded email subjects after HTML escaping. Unauthenticated attackers can send crafted emails to monitored mailboxes with nested MIME encoded-words to inject JavaScript. The payload executes in technician browser sessions when they open the ingested ticket. Because ticket ingestion happens automatically over IMAP, no attacker authentication or prior access to the GestSup application is required.
Critical Impact
Unauthenticated attackers can achieve stored JavaScript execution in authenticated technician sessions by sending a crafted email to a monitored mailbox, enabling session abuse and follow-on actions against the ticketing system.
Affected Products
- GestSup versions prior to 3.2.62
- GestSup deployments configured with the IMAP OAuth connector
- Technician user interface rendering ingested ticket subjects
Discovery Timeline
- 2026-09-29 - CVE-2026-102374 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-102374
Vulnerability Analysis
GestSup ingests email into tickets through its IMAP OAuth connector. Email subjects encoded per RFC 2047 (MIME encoded-words) are decoded before storage and display. The connector applies HTML escaping to the subject, then performs a second MIME decode pass over the already-escaped output. Attackers exploit this ordering by nesting encoded-words so that dangerous characters materialize only after the escape step has run. The final string reaches the technician interface with active markup intact, producing stored XSS. Exploitation requires user interaction from a technician who opens the crafted ticket, but does not require attacker authentication.
Root Cause
The root cause is incorrect ordering of output encoding and input decoding in the IMAP subject handling path. Sanitization must be the last transformation applied before rendering. Re-decoding after escaping reintroduces the characters (<, >, ") that the escape step was meant to neutralize, defeating the protection.
Attack Vector
An unauthenticated remote attacker sends an email to any mailbox polled by the GestSup OAuth IMAP connector. The Subject header carries a MIME encoded-word whose decoded content is itself an encoded-word wrapping a JavaScript payload. GestSup escapes the outer decoded form, then decodes again, yielding raw script markup stored on the ticket. When a technician views the ticket, the script executes with the technician's session privileges. See the VulnCheck Advisory for GestSup XSS and the SPIIZN Blog RCE Article for exploitation details.
Detection Methods for CVE-2026-102374
Indicators of Compromise
- Inbound emails to monitored mailboxes containing nested =?charset?B?...?= or =?charset?Q?...?= MIME encoded-words in the Subject header.
- Ticket records whose stored subject field contains <script, onerror=, onload=, or javascript: substrings after ingestion.
- Unexpected outbound requests from technician browsers immediately after opening a ticket, indicating script execution.
Detection Strategies
- Inspect the Subject column of the tickets database for HTML/JavaScript control characters that should have been escaped.
- Enable Content Security Policy (CSP) reporting on the GestSup web interface and alert on report submissions triggered by ticket views.
- Correlate IMAP fetch logs with ticket creation events to identify emails whose subjects were transformed multiple times during decoding.
Monitoring Recommendations
- Log and review all outbound requests from technician workstations to unrecognized domains after ticket interactions.
- Monitor authentication and privilege-change events in GestSup that follow shortly after a technician opens a newly ingested ticket.
- Retain full raw email headers for tickets created via the OAuth IMAP connector to support retrospective analysis.
How to Mitigate CVE-2026-102374
Immediate Actions Required
- Upgrade GestSup to version 3.2.62 or later using the GestSup Patch 3.2.62.
- Restrict which mailboxes the OAuth IMAP connector polls until the patch is applied.
- Instruct technicians to avoid opening tickets sourced from unknown external senders until remediation is complete.
Patch Information
The vendor addressed the vulnerability in GestSup 3.2.62. Refer to the GestSup Changelog for release notes and the GestSup Download Page to obtain the current stable build. The fix reorders decoding and escaping so that HTML sanitization is applied after all MIME decoding passes.
Workarounds
- Disable the OAuth IMAP connector until GestSup 3.2.62 can be deployed.
- Front the GestSup web interface with a web application firewall rule that blocks responses containing raw <script markup inside ticket subject fields.
- Deploy a strict Content-Security-Policy header disallowing inline scripts on the technician interface to reduce payload viability.
# Example strict CSP header for the GestSup technician interface
Content-Security-Policy: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
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

