dbcve.org
Quiter GatewayApplication · Quiter

CVE-2025-40714

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 campo id_factura in /<Client>FacturaE/listado_facturas_ficha.jsp.

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 unauthenticated attackers to inject arbitrary SQL commands through the id_factura parameter in the /<Client>FacturaE/listado_facturas_ficha.jsp endpoint. This enables complete database compromise including unauthorized data retrieval, insertion, modification, and deletion.

MitigationUpgrade to Quiter Gateway version 4.7.0 or later. Until patching is possible, implement parameterized queries or prepared statements for the id_factura parameter and apply least-privilege database access controls to reduce impact.

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 installation
    Locate the Quiter Gateway application on the system. Look for the web application directory containing the /<Client>FacturaE/ path structure, or check running web services for JSP applications serving the 'FacturaE' module.
    Affected if Quiter Gateway is installed and the FacturaE module is present on the server
  2. Determine installed Quiter Gateway version
    Check the application version by examining version files, WAR file manifests, or the application admin interface. Common locations include WEB-INF/MANIFEST.MF, version.properties files, or the application's 'About' page.
    Affected if The installed version is less than 4.7.0 (e.g., 4.6.x, 4.5.x, etc.)
  3. Verify vulnerable endpoint exists
    Locate the listado_facturas_ficha.jsp file within the application directory structure under the FacturaE module path. The path follows the pattern: /<context>/<Client>FacturaE/listado_facturas_ficha.jsp
    Affected if The listado_facturas_ficha.jsp file exists in the application, indicating the vulnerable component is present
  4. Confirm parameter exposure
    Review web server access logs or proxy configurations for requests to the /<Client>FacturaE/listado_facturas_ficha.jsp endpoint with the id_factura parameter. This can indicate active use of the vulnerable endpoint.
    Affected if The id_factura parameter is accepted by the endpoint without sanitization, which is the case for all versions prior to 4.7.0

The environment is affected if Quiter Gateway version is identified as less than 4.7.0 and the FacturaE module with the listado_facturas_ficha.jsp endpoint is present.

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. Until patching is possible, implement parameterized queries or prepared statements for the id_factura parameter and apply least-privilege database access controls to reduce impact.

Recommended fix Moderate confidence

4.7.0 or later

  1. Identify all instances of Quiter Gateway running version less than 4.7.0
  2. Backup the current installation and database before upgrading
  3. Obtain Quiter Gateway version 4.7.0 or later from the vendor (Quiter)
  4. Follow vendor-provided upgrade procedures to update to version 4.7.0
  5. Verify the upgrade was successful by checking the version number
  6. Test the application functionality, particularly the /<Client>FacturaE/listado_facturas_ficha.jsp endpoint to confirm the SQL injection is resolved

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

Fix this in Quiter Gateway Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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