dbcve.org
GestsupApplication

CVE-2026-22198

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to after 3.2.56 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GestSup versions prior to 3.2.60 contain a pre-authentication stored cross-site scripting (XSS) vulnerability in the API error logging functionality. By sending an API request with a crafted X-API-KEY header value (for example, to /api/v1/ticket.php), an unauthenticated attacker can cause attacker-controlled HTML/JavaScript to be written to log entries. When an administrator later views the affected logs in the web interface, the injected content is rendered without proper output encoding, resulting in arbitrary script execution in the administrator’s browser session.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GestSup versions prior to 3.2.60 have a stored XSS vulnerability in the API error logging. Unauthenticated attackers can send API requests with malicious X-API-KEY headers to /api/v1/ticket.php, causing attacker-controlled HTML/JavaScript to be written to server log entries. When administrators view these logs in the web interface, the injected content renders without output encoding, executing arbitrary scripts in the admin's browser.

MitigationUpgrade to GestSup version 3.2.60 or later which contains the security fix. As a temporary workaround, implement input validation on the X-API-KEY header to reject special characters before logging, and ensure proper output encoding is applied when displaying log entries in the admin interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GestsupApplication
Affected:<= 3.2.56

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GestSup version
    Locate the version file or check the admin interface footer/version page. Common locations include a version.php file in the application root, or the 'System' or 'About' section in the web UI.
    Affected if The installed version is 3.2.56 or lower (any version prior to 3.2.60).
  2. Verify API endpoint accessibility
    Confirm that the endpoint /api/v1/ticket.php exists and responds to requests. This can be done by attempting a request to this endpoint or checking the file system for its presence.
    Affected if The endpoint /api/v1/ticket.php is present and accessible to unauthenticated users.
  3. Confirm admin log viewing capability
    Access the admin panel and navigate to the log viewing section where API error logs are displayed. Verify that administrators can view entries written to server logs.
    Affected if The admin interface includes a feature to view API error logs, as this is required for the stored XSS to execute.
  4. Identify X-API-KEY header logging behavior
    Send a test API request to /api/v1/ticket.php with a custom X-API-KEY header containing a harmless marker string, then check if this header value appears in the server logs without sanitization.
    Affected if The X-API-KEY header value is logged as-is without sanitization or encoding, indicating the vulnerability is present.

A system is affected if it runs GestSup version 3.2.56 or lower, has the /api/v1/ticket.php endpoint accessible, and logs the X-API-KEY header without sanitization before displaying those logs to administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.2.56
Interim mitigation

Upgrade to GestSup version 3.2.60 or later which contains the security fix. As a temporary workaround, implement input validation on the X-API-KEY header to reject special characters before logging, and ensure proper output encoding is applied when displaying log entries in the admin interface.

Recommended fix High confidence

3.2.60 or later

  1. 1. Backup your current Gestsup installation and database before proceeding with any upgrade.
  2. 2. Download Gestsup version 3.2.60 or later from the official vendor source (gestsup.fr).
  3. 3. Install the updated version following the vendor's standard upgrade procedure.
  4. 4. Verify the upgrade was successful by logging into the administration interface.
  5. 5. Confirm the X-API-KEY header injection point at /api/v1/ticket.php is now properly sanitized.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gestsup Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data