Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
DeliverySend GET to thread.php with threadedit=ID
-
ExploitEnumerate sequential comment IDs
-
ExecutionServer skips ownership check
-
ImpactRead private comments from other tickets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated GestSup account of any privilege level (PR:L) with network access to the web application; no user interaction and no special or non-default configuration is needed. Exploitation targets the threadedit parameter of thread.php, which loads ticket comments without validating that the requesting user owns the ticket, so an attacker simply iterates sequential comment IDs. The limiting factors are the authentication requirement (self-service or granted account needed) and the read-only nature of the flaw - it discloses private comment content but cannot modify data or affect availability. All GestSup versions before 3.2.62 are affected; upgrading to 3.2.62 removes the exposure. |
| Impact | This is a CWE-639 insecure-direct-object-reference (IDOR) authorization flaw in GestSup's ticket comment loader. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) scores 7.1 and is internally consistent with the description: network-reachable, low complexity, requires an authenticated low-privilege account (PR:L), no user interaction, and a confidentiality-only impact (VC:H) with no integrity or availability effect. There is no CISA KEV listing, no EPSS score, and no public exploit code referenced - so this is 'no public exploit identified at time of analysis,' NOT active exploitation. The realistic risk is moderate rather than urgent: the confidentiality impact can be high (private comments across all tickets are readable by any authenticated user via trivial sequential ID enumeration), but exploitation is gated behind holding a valid account, the impact is read-only, and the affected product has a limited deployment footprint. A patch is available from the vendor (v3.2.62), which materially lowers the priority for organizations that can update. Note the input Tag 'Authentication Bypass' conflicts with the CVSS PR:L metric - this is a post-authentication authorization/IDOR issue, not an authentication bypass; treat the tag as mislabeled. |
| Exploit ScenarioDerived | A low-privileged authenticated GestSup user (e.g. a standard helpdesk requester) sends requests to thread.php varying the threadedit parameter across sequential comment IDs. Because ticket ownership is never validated, the server returns private comments belonging to other users' tickets, letting the attacker harvest confidential ticket discussions. No public proof-of-concept is referenced, though the VulnCheck advisory documents the technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Authenticated users of GestSup before 3.2.62 can read private comments belonging to other users' tickets by manipulating the threadedit parameter in thread.php, because the comment loader never verifies that the requester owns the referenced ticket. Any valid account, even a low-privilege self-service one, is enough to iterate sequential comment IDs and harvest confidential ticket discussions over the network with no user interaction required. No public exploit code or active exploitation has been identified at time of analysis, and the vendor has released version 3.2.62 to close the exposure.
RemediationAI
Upgrade to GestSup 3.2.62, which the vendor identifies as the fixed release; the stable patch package is available at https://gestsup.fr/index.php?page=download&channel=stable&version=3.2.62&type=patch and general downloads and release notes are at https://gestsup.fr/index.php?page=download and https://gestsup.fr/index.php?page=changelog. Vendor-released patch: 3.2.62. Because exploitation requires an authenticated session rather than a network position, the most effective compensating control is to tightly control who can obtain a GestSup account: disable or restrict self-registration and review existing low-privilege/self-service accounts, accepting the trade-off that legitimate end-user ticket submission and comment viewing will be curtailed for accounts that are removed or locked down. Until patching, administrators can monitor web server and proxy logs for repeated GET/POST requests to thread.php carrying incremental threadedit values from a single session and rate-limit or block those sources; this is a detective control that does not eliminate the flaw and can be evaded by slow, low-volume enumeration. Restricting network access to the GestSup instance to trusted internal address ranges reduces the pool of potential authenticated attackers but does not protect against malicious or compromised internal users, and a WAF rule that validates the authenticated user against the requested comment's ticket before proxying the request is only feasible with custom application-aware logic, since generic signature-based filtering cannot express the ownership check.
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
GestSup is a PHP-based IT service management and ticketing application. The flaw is a classic insecure direct object reference (CWE-639) in the comment-loading path of thread.php: when the threadedit parameter supplies a comment identifier, the application retrieves and returns the associated comment without performing an ownership or authorization check against the requesting user's session. Because comment identifiers are sequential and predictable, an authenticated attacker can walk the ID space and reconstruct private discussions from tickets they have no rights to. The vendor-supplied CPE cpe:2.3:a:gestsup:gestsup:*:*:*:*:*:*:*:* indicates the entire GestSup product line prior to the fixed build is affected, not a single edition. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N confirms the defect is remotely reachable, requires only low-level privileges, needs no user interaction and no non-default configuration, and is purely confidentiality-impacting - there is no integrity or availability loss, which matches the read-only nature of the comment disclosure.
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:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable IDOR requiring only a low-privilege authenticated account (PR:L), low complexity, no UI; read-only disclosure of private data so C:H, I:N, A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
GestSup versions before 3.2.62 fail to validate ticket ownership when loading comments via the threadedit parameter in thread.php. Authenticated attackers can enumerate sequential comment IDs to read private comments from other users' tickets without proper authorization checks.
Executive ViewAI
GestSup versions prior to 3.2.62 contain a high-severity vulnerability that allows any user with a valid account, including low-privilege self-service users, to read private comments on other users' tickets. This exposes confidential support discussions and potentially sensitive business or customer information to unauthorized internal parties. Security leadership should prioritize immediate patching to prevent data leakage and maintain trust in the support platform.
Apply vendor patch.
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
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-88597
GHSA-wcm4-67q4-6r6m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB