dbcve.org
GestsupApplication

CVE-2026-22197

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 multiple SQL injection vulnerabilities in the asset list functionality. Multiple request parameters used to filter, search, or sort assets are 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 multiple SQL injection vulnerabilities in the asset list functionality. Multiple request parameters used to filter, search, or sort assets are incorporated into SQL queries without sufficient input sanitization, allowing an authenticated attacker to manipulate database queries and potentially access or modify database contents.

MitigationUpgrade to GestSup version 3.2.60 or later which contains the security fix. Until then, restrict access to authenticated users only and consider implementing additional input validation at the application layer as a compensating control.

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. Determine installed GestSup version
    Locate the version number displayed in the GestSup application interface (typically found in the footer, about page, or admin panel) or check version information in application configuration files
    Affected if Installed version is 3.2.56 or earlier, or any version prior to 3.2.60
  2. Identify if asset list functionality is enabled
    Access the asset management section of the application and confirm the asset list feature is accessible and functional
    Affected if Asset list feature is available and operational in the environment
  3. Verify authentication requirements for asset endpoints
    Test access to asset list URLs or API endpoints without providing credentials to determine if authentication is enforced
    Affected if Asset list endpoints are accessible without authentication or with low-privilege user accounts
  4. Check for parameter manipulation in asset filtering
    Examine how asset search, filter, and sort parameters are handled by observing HTTP requests and responses when using these features
    Affected if Parameters used for filtering, searching, or sorting assets can be modified without input validation errors being triggered
  5. Review database query handling for asset operations
    If database logging or application debugging is available, inspect logs for SQL query construction when asset list parameters are supplied
    Affected if SQL queries incorporate user-supplied parameters directly without apparent sanitization or parameterized query usage

Environment is affected if GestSup version is 3.2.56 or earlier and the asset list functionality is accessible to the attacker, allowing SQL injection via unsanitized parameters in asset search, filter, or sort operations.

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. Until then, restrict access to authenticated users only and consider implementing additional input validation at the application layer as a compensating control.

Recommended fix High confidence

Gestsup 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 vendor source (gestsup.fr).
  3. 3. Follow the vendor's documented upgrade procedure for installing the new version.
  4. 4. Verify the upgrade was successful by checking the Gestsup version number in the application.
  5. 5. Test the asset list functionality to confirm normal operation after the upgrade.

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-22197 — 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-22197 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