dbcve.org
GestsupApplication

CVE-2026-22196

HIGH · 8.1 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to after 3.2.56 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 SQL injection vulnerability in ticket creation functionality. User-controlled input provided during ticket creation is incorporated into SQL queries without sufficient neutralization, allowing an authenticated attacker to manipulate database queries. Successful exploitation can result in unauthorized access to or modification of database contents depending on database privileges.

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 contain a SQL injection vulnerability in the ticket creation functionality where user-controlled input is incorporated into SQL queries without proper parameterization or sanitization, allowing authenticated attackers to manipulate database queries.

MitigationUpgrade to GestSup version 3.2.60 or later and refactor ticket creation code to use parameterized queries/prepared statements for all database operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify installed GestSup version
    Locate the version number in the GestSup application (typically displayed in the admin panel, footer, or in a version file within the installation directory)
    Affected if The installed version is 3.2.56 or any earlier version, since versions prior to 3.2.60 and specifically <= 3.2.56 are affected
  2. Verify ticket creation functionality is accessible
    Confirm that the ticket creation feature is enabled and accessible to authenticated users in the GestSup system
    Affected if The ticket creation module is active and users can submit new tickets through the interface
  3. Confirm lack of parameterized queries in ticket creation code
    Examine the source code handling ticket creation (look for SQL query construction files related to ticket submission) to verify whether user input is directly incorporated into SQL queries without prepared statements or parameterization
    Affected if The ticket creation code builds SQL queries by directly concatenating or interpolating user-supplied input into query strings rather than using bound parameters

You are affected if your GestSup installation runs version 3.2.56 or earlier, has the ticket creation feature enabled, and the ticket creation code directly incorporates user input into SQL queries without using parameterized queries or prepared statements.

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 and refactor ticket creation code to use parameterized queries/prepared statements for all database operations.

Recommended fix High confidence

3.2.60

  1. 1. Backup the current Gestsup installation and database before proceeding with any upgrade.
  2. 2. Download Gestsup version 3.2.60 or later from the official source (gestsup.fr).
  3. 3. Review the official upgrade documentation provided with the new version for specific installation instructions.
  4. 4. Apply the upgrade following the standard upgrade procedure for Gestsup.
  5. 5. Verify the upgrade was successful by logging into the application.
  6. 6. Test the ticket creation functionality to confirm the SQL injection vulnerability has been remediated.
  7. 7. Verify that existing functionality remains intact after the upgrade.

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

Fix this in Gestsup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22196 — 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-22196 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