dbcve.org
Quiter GatewayApplication · Quiter

CVE-2025-40717

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SQL injection vulnerability in versions prior to 4.7.0 of Quiter Gateway by Quiter. This vulnerability allows an attacker to retrieve, create, update and delete databases through the pagina.filter.categoria mensaje in /QuiterGatewayWeb/api/v1/sucesospagina.

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

SQL injection vulnerability in Quiter Gateway versions prior to 4.7.0 allows remote attackers to inject malicious SQL code via the pagina.filter.categoria mensaje parameter in the /QuiterGatewayWeb/api/v1/sucesospagina API endpoint. This enables full database manipulation including reading, creating, updating, and deleting database records.

MitigationUpgrade to Quiter Gateway version 4.7.0 or later. If immediate upgrade is not possible, implement input validation and parameterized queries on the vulnerable parameter, and consider restricting network access to the API endpoint.

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
Quiter GatewayApplication
Affected:< 4.7.0

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

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

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 Quiter Gateway version
    Check the installed version of Quiter Gateway by accessing the product's about page, checking the software manifest, or querying the API endpoint /QuiterGatewayWeb/api/version if available. Compare the version number to the affected range (versions prior to 4.7.0).
    Affected if The installed version is lower than 4.7.0
  2. Confirm API endpoint exposure
    Verify that the /QuiterGatewayWeb/api/v1/sucesospagina endpoint is accessible from the network by attempting a GET or POST request to this endpoint. Check network firewall rules and web server configuration to determine if this API path is publicly or internally exposed.
    Affected if The /QuiterGatewayWeb/api/v1/sucesospagina endpoint is reachable and responds to requests
  3. Test vulnerable parameter
    Send a crafted request to the /QuiterGatewayWeb/api/v1/sucesospagina endpoint with a SQL injection payload in the 'pagina.filter.categoria' or 'mensaje' parameter (for example: ' OR '1'='1). Observe if the application returns database errors, unexpected data, or behaves differently than expected.
    Affected if The application accepts and processes the vulnerable parameter without proper input validation or parameterized queries, resulting in SQL error messages or unexpected behavior

A user is affected if Quiter Gateway version is below 4.7.0 AND the /QuiterGatewayWeb/api/v1/sucesospagina endpoint is accessible with the vulnerable parameter accepting unsanitized input.

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 4.7.0 or later
Fixed in 4.7.0
Interim mitigation

Upgrade to Quiter Gateway version 4.7.0 or later. If immediate upgrade is not possible, implement input validation and parameterized queries on the vulnerable parameter, and consider restricting network access to the API endpoint.

Recommended fix Moderate confidence

Quiter Gateway 4.7.0

  1. Identify current Quiter Gateway version by checking the application or system information
  2. Backup the current Quiter Gateway installation including all databases and configuration files
  3. Schedule a maintenance window for the upgrade process
  4. Upgrade Quiter Gateway to version 4.7.0 following the vendor's standard upgrade procedure
  5. Verify the upgrade was successful by checking the new version number
  6. Confirm the vulnerability is resolved by testing the /QuiterGatewayWeb/api/v1/sucesospagina endpoint with the pagina.filter.categoria parameter

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

Fix this in Quiter Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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