CVE-2025-40715 is a critical SQL injection flaw in Quiter Gateway, with a CVSS score of 9.8. INCIBE says QuiterGatewayWeb 4.7.0 and the matching QMSCliente and QISClient builds fix it. Treat any instance reachable from untrusted networks as exposed until you have confirmed the fix, and review your logs for unexpected requests.
What's affected
- Product: Quiter Gateway, a Java WAR on Apache Tomcat used to manage car dealerships and workshops. INCIBE lists versions below 4.7.0 as affected.
- Fixed version: INCIBE updated its advisory on 8 July 2025 to say Quiter released fixed builds: QuiterGatewayWeb 4.7.0, QMSCliente 1.0.15 and QISClient 2.0.1-SNAPSHOT. It also says Quiter applied the fix to all affected customers, and that an external auditor verified it.
- Severity: Critical, CVSS 9.8 (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
- Weakness: CWE-89.
- Published: 2025-07-08.
The vulnerable input is the mensaje parameter of the /QISClient/api/v1/sucesospaginas API. The record says an attacker could retrieve, create, update and delete data in the database.
INCIBE advisory INCIBE-2025-0349 lists eleven Quiter Gateway CVEs. CVE-2025-40711 to CVE-2025-40717 are the seven critical SQL injection flaws, each in a different input. The other four are medium severity.
How to check if you're exposed
The advisory lists three deployable components. If they are WAR files on your Tomcat server, you can read the packaged manifest, if it carries a version:
unzip -p QuiterGatewayWeb.war META-INF/MANIFEST.MF
If the manifest has no version, ask Quiter or check your deployment records. The advisory does not describe another way to read it.
You can also run your dependency manifests and container images through the free in-browser scan to see which known CVEs affect the packages you ship. It will not find a flaw inside a vendor appliance or an unmanaged install, so keep an inventory of those too.
What to do now
- Identify every copy of Quiter Gateway you run, including test and forgotten ones.
- Check the version of each component, not only the gateway. The fix spans three separate builds.
- Until that is done, remove public access where you can. Put the application behind a VPN, a network allow list or a web application firewall rule, and watch the access and database logs for unusual requests to the endpoint named above.
- Record the outcome, including the date, the version you ended on and who confirmed it, so a later audit has something to read.
- Add the product to your continuous monitoring so a future CVE against it reaches you without a manual search.
Why it matters
SQL injection happens when an application builds a database query by gluing user input into the query text. The database cannot tell where the developer's command ends and the visitor's data begins, so a crafted value can change what the query does. The class is catalogued as CWE-89 (SQL injection).
The usual fix is a parameterized query, where the SQL text and the values travel separately. Input validation helps as a second layer, but it is not a substitute. Because this flaw needs no login and no click from a victim, anything that can reach the page over the network is in range.
The record's KEV flag is false, so CISA does not list it as known to be exploited, and nothing in the sources here says it is being exploited in the wild.
Quick check
What does the score of 9.8 mean for Quiter Gateway?
The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H reads as network reachable, low complexity, no privileges and no user interaction. The impact ratings are confidentiality high, integrity high, availability high. Use it to rank the work, then confirm exposure for your own deployment.
Is escaping the parameter enough to fix this?
Escaping is fragile and easy to get wrong in one place out of many. Parameterized queries are the reliable fix because the value is never treated as SQL. If you maintain the code, change the query itself rather than patching the symptom.
Sources
Last reviewed: 18 October 2026.
