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-102373 Overview
CVE-2026-102373 is an authorization flaw in GestSup, an open-source IT ticketing and helpdesk platform, affecting all versions before 3.2.62. The thread.php endpoint fails to validate ticket ownership when loading comments through the threadedit parameter. Authenticated attackers can enumerate sequential comment identifiers to read private comments belonging to other users' tickets. The vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, commonly known as an Insecure Direct Object Reference (IDOR).
Critical Impact
Any authenticated GestSup user can read confidential ticket comments from other users, exposing credentials, internal communications, and sensitive support data.
Affected Products
- GestSup versions prior to 3.2.62
- GestSup helpdesk and ticketing installations exposing thread.php
- On-premises GestSup deployments accepting authenticated user sessions
Discovery Timeline
- 2026-09-29 - CVE-2026-102373 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-102373
Vulnerability Analysis
GestSup handles ticket comment retrieval through the thread.php script, which accepts a threadedit parameter identifying the comment to load. The application uses this parameter to query comment records but omits a check verifying that the requesting user owns or has access to the parent ticket. Because comment identifiers are sequential integers, an authenticated attacker can iterate through values and retrieve arbitrary comments across the entire ticketing database. Private comments in helpdesk workflows often contain reset passwords, internal notes, escalation details, and personally identifiable information, so unauthorized read access has direct confidentiality impact.
Root Cause
The root cause is a missing authorization check on a user-controlled object identifier. The threadedit parameter is treated as a trusted reference to a comment record, and the backend query returns the record without joining or validating against the ticket's owner, assignee, or permission scope. This is a textbook Insecure Direct Object Reference pattern under [CWE-639], where authentication is enforced but per-object authorization is not.
Attack Vector
Exploitation requires only a low-privileged authenticated account on the GestSup instance. An attacker logs in, opens a legitimate ticket to observe the request format for thread.php, then issues repeated requests with incrementing threadedit values. Each response discloses the content of a comment attached to a ticket the attacker does not own. No user interaction from victims is required, and the attack can be scripted to enumerate the entire comment table. Full exploitation details and request traces are documented in the VulnCheck Advisory for GestSup and the Spiizn technical write-up.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-102373
Indicators of Compromise
- Repeated authenticated requests to thread.php with sequentially incrementing threadedit parameter values from a single session or IP.
- Unusual volume of successful HTTP 200 responses to thread.php from a single user account within a short time window.
- Access to threadedit values corresponding to tickets not assigned to or created by the requesting user.
Detection Strategies
- Correlate web server logs against the GestSup ticket-ownership table to flag reads of comments outside the authenticated user's ticket scope.
- Implement rate-based detection on thread.php requests per authenticated session to identify enumeration behavior.
- Add application-layer logging that records user_id, ticket_id, and threadedit values for every comment fetch to support forensic review.
Monitoring Recommendations
- Monitor for spikes in thread.php request volume tied to non-administrator accounts.
- Alert on GestSup users accessing comment identifiers spanning wide numeric ranges within short intervals.
- Review authentication logs for accounts created shortly before high-volume thread.php access, which may indicate attacker-provisioned users.
How to Mitigate CVE-2026-102373
Immediate Actions Required
- Upgrade all GestSup instances to version 3.2.62 or later using the GestSup 3.2.62 patch release.
- Audit historical thread.php access logs for enumeration patterns against threadedit prior to patch deployment.
- Rotate credentials, tokens, or secrets that may have been shared in ticket comments if evidence of enumeration is found.
Patch Information
GestSup addressed the missing authorization check in version 3.2.62. The vendor publishes the fixed build on the GestSup download page and documents the change in the GestSup changelog. Apply the patch directly against the running installation and validate that thread.php enforces ticket ownership post-upgrade.
Workarounds
- Restrict access to the GestSup web interface to trusted networks or VPN users until patching is complete.
- Disable or tightly scope non-administrator accounts on affected instances to limit the pool of accounts that can exploit the flaw.
- Place a reverse proxy or WAF rule in front of thread.php that validates the requesting session's ticket scope before forwarding the request.
# Example WAF rule concept: block requests to thread.php that iterate threadedit rapidly
# ModSecurity pseudo-rule
SecRule REQUEST_URI "@contains /thread.php" \
"id:1026102373,phase:2,deny,status:429,\
msg:'GestSup threadedit enumeration attempt',\
chain"
SecRule ARGS:threadedit "@rx ^[0-9]+$" \
"chain"
SecRule IP:threadedit_count "@gt 20" \
"setvar:ip.threadedit_count=+1,expirevar:ip.threadedit_count=60"
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

