dbcve.org
GestsupApplication

CVE-2026-22195

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 the search bar functionality. User-controlled search input 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 · moderate confidence

GestSup versions prior to 3.2.60 contain a SQL injection vulnerability in the search bar functionality where user-controlled search input is directly incorporated into SQL queries without proper neutralization, allowing authenticated attackers to manipulate database queries.

MitigationUpgrade to GestSup version 3.2.60 or later which contains the security fix; alternatively, implement parameterized queries or prepared statements for all database interactions involving user input.

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 if GestSup is installed
    Locate the GestSup application directory or check web server logs for GestSup access. Common locations include /var/www/html/gestsup or similar web directories. Look for the typical GestSup login page or admin interface.
    Affected if GestSup is present in the environment
  2. Determine installed GestSup version
    Access the GestSup admin interface and navigate to the About or Information page typically found in the admin/settings area. Alternatively, check version.php or similar version files in the installation directory if accessible.
    Affected if The installed version is 3.2.56 or any version prior to 3.2.56
  3. Verify authentication is enabled
    Confirm that user authentication is active on the GestSup instance. Check if the login page accepts credentials and users can authenticate to access the main interface.
    Affected if Authentication is enabled and users can log in to access the application
  4. Confirm search bar functionality is accessible
    Log into GestSup and locate the search bar feature in the user interface. This is typically found on the main dashboard or in specific module areas where search functionality exists.
    Affected if The search bar functionality is accessible to authenticated users

A user is affected if GestSup version 3.2.56 or earlier is installed, authentication is enabled, and the search bar feature is accessible to at least one authenticated user account.

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; alternatively, implement parameterized queries or prepared statements for all database interactions involving user input.

Recommended fix High confidence

Gestsup version 3.2.60 or later

  1. 1. Backup the current Gestsup installation and database before proceeding with any changes
  2. 2. Download Gestsup version 3.2.60 or later from the official source at gestsup.fr
  3. 3. Follow the official Gestsup upgrade documentation to install the new version
  4. 4. Verify the upgrade was successful by checking the version number in the admin interface
  5. 5. Test the search bar functionality to confirm it operates normally

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

Fix this in Gestsup Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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