Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTML email to monitored mailbox
-
DeliveryGestSup IMAP connector ingests unsanitized body
-
ExploitStored payload lands in ticket description/reply
-
ExecutionTechnician opens ticket in browser
-
PersistScript executes in GestSup origin
-
ImpactExfiltrate ticket data / perform actions as technician
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that the GestSup instance has the IMAP LOGIN email connector enabled and configured to poll a mailbox reachable by the attacker (a monitored support inbox) - this is the specific feature that turns inbound email into ticket content. Delivery itself needs no authentication and no special attacker privileges; the attacker only needs to know or guess the monitored email address. Exploitation is LIMITED by requiring victim interaction (UI:P): a technician must actually open the malicious ticket/reply in their browser for the payload to fire, and impact is confined to the technician's authenticated session (ticket data theft, actions-as-technician) rather than direct server compromise. Environments not using the IMAP LOGIN connector are not exposed via this vector. |
| Impact | This is a moderate-priority, real-but-bounded issue. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P) scores 5.3 and indicates a network-reachable, low-complexity flaw requiring no attacker authentication - the injection is delivered simply by emailing the monitored IMAP mailbox, which is a genuinely low bar. The counterweight is impact and interaction: the vector assigns no impact to the primary vulnerable system (VC:N/VI:N/VA:N) and only low confidentiality/integrity to the subsequent system (SC:L/SI:L) - i.e. the payload only executes in a technician's browser (UI:P/passive interaction), not on the GestSup server itself, so this is classic stored XSS rather than server compromise. No EPSS score, KEV listing, POC, or SSVC decision data is provided, so exploitation-probability and automatability signals are absent - this should be read as 'no public exploit identified at time of analysis,' NOT as low real risk. The signals are internally consistent (network reachable, unauthenticated delivery, victim-side execution, limited impact) with no contradictions to flag. A patch (3.2.62) is confirmed available from the vendor, which raises actionability. Net: patch it, but it is not a drop-everything critical. |
| Exploit ScenarioDerived | An attacker with no credentials sends an email to the support mailbox that GestSup polls via its IMAP LOGIN connector, embedding a <script> tag or an event-handler attribute (e.g. onerror) in the HTML body. GestSup ingests the body unsanitized into a new ticket description or reply, and when a helpdesk technician later opens that ticket in their browser the JavaScript runs in the GestSup application origin, enabling theft of ticket data or actions performed as the technician. No public exploit code is identified at time of analysis, though the technique is trivially reproducible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Stored cross-site scripting in GestSup versions before 3.2.62 lets unauthenticated attackers plant arbitrary JavaScript in ticket descriptions and replies by sending crafted emails to a monitored support mailbox, which then executes in a technician's browser when the ticket is opened. The root problem is that the IMAP LOGIN connector fails to sanitize HTML email bodies, so any instance that has that connector enabled and polling an attacker-reachable inbox is exposed; delivery requires no authentication or special privileges, only knowledge or guessing of the mailbox address, and the payload only fires if a technician actually opens the malicious ticket, limiting impact to that technician's authenticated session (ticket data theft and actions performed as that technician) rather than server compromise. A vendor patch is available (fixed in 3.2.62) and no public exploit identified at time of analysis; the issue carries a moderate CVSS of 5.3 and is not confirmed actively exploited (CISA KEV).
RemediationAI
Vendor-released patch: 3.2.62 - upgrade GestSup to 3.2.62 or later using the official patch package at https://gestsup.fr/index.php?page=download&channel=stable&version=3.2.62&type=patch (see also the changelog at https://gestsup.fr/index.php?page=changelog and download page at https://gestsup.fr/index.php?page=download). Because the flaw is only reachable through the IMAP LOGIN email ingestion path, an effective interim mitigation when upgrading is not immediately possible is to disable the IMAP LOGIN connector in GestSup's administration settings so inbound email is no longer converted into ticket content; the trade-off is loss of automatic email-to-ticket automation for the affected mailbox. A narrower alternative is to keep the connector but harden the mailbox ingestion path - restrict the monitored mailbox to trusted senders and/or strip or quarantine HTML parts and convert inbound messages to plain text at the mail gateway before GestSup retrieves them - which reduces but does not fully eliminate the attack surface since sanitization still ultimately depends on the application. Administrators should also consider a restrictive Content-Security-Policy on the GestSup web UI. No additional vendor workaround is documented beyond the fixed release.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a CWE-79 improper neutralization of input during web page generation (cross-site scripting) flaw in GestSup, an open-source PHP/MySQL helpdesk and ticket management application. The IMAP LOGIN connector is the feature that converts inbound email from a monitored mailbox into tickets, replies and comments; because the HTML body of those messages is not sanitized on ingest and is later rendered without adequate output encoding in the technician-facing ticket UI, attacker-supplied markup such as <script> tags and event handlers survives storage and executes in the browser of any technician viewing the affected ticket. Execution occurs in the origin of the GestSup web application and within the victim technician's authenticated session, which is why the assessed vector carries a scope change (S:C) with low confidentiality and integrity impact on subsequent systems, network attack vector, low complexity, no privileges required, and user interaction required (UI:P) - reflecting that the payload is delivered silently by email but detonates only when a technician opens the ticket. Affected technology therefore spans the GestSup application itself, the IMAP email ingestion path, and the browser rendering context of the ticketing UI. CPE data (cpe:2.3:a:gestsup:gestsup:*:*:*:*:*:*:*:*) confirms the wildcard covers all releases before the fixed 3.2.62.
Know when Gestsup gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Unauthenticated email delivery (PR:N, AV:N/AC:L) but payload executes only when a technician views the ticket (UI:R) in a different security context (S:C), yielding limited C/I and no availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
GestSup versions before 3.2.62 fail to properly sanitize HTML email bodies in the IMAP LOGIN connector, allowing unauthenticated attackers to store arbitrary JavaScript in ticket descriptions and replies. Attackers can send emails to the monitored mailbox containing script tags and event handlers that execute in technician browsers, enabling ticket data theft and unauthorized actions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Related Vulnerabilities in GestSup XSS and Access Control Vulnerabilities
View all 3Gestsup before 3.2.10 allows account takeover through the password recovery functionality (remote). Rated critical sever
Unauthenticated remote code execution affects GestSup, the PHP-based IT asset and ticket management application, in all
GestSup through version 3.2.60 fails to implement CSRF protections, enabling attackers to forge requests that execute ac
GestSup versions before 3.2.60 allow authenticated attackers to execute SQL injection attacks through insufficiently san
GestSup prior to version 3.2.60 is vulnerable to SQL injection in the ticket creation feature, allowing authenticated at
Authenticated attackers can exploit SQL injection in GestSup's search functionality (versions before 3.2.60) to manipula
GestSup before version 3.2.60 contains a pre-authentication stored XSS vulnerability in API error logging that allows un
EUVD-2026-88596
GHSA-ghhh-8g6j-jh47
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB