dbcve.org
Quiter GatewayApplication · Quiter

CVE-2025-40721

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Reflected Cross-site Scripting (XSS) vulnerability in versions prior to 4.7.0 of Quiter Gateway by Quiter. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending a malicious URL trhough the id_factura parameter 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

Reflected XSS vulnerability in Quiter Gateway (versions prior to 4.7.0) where the id_factura parameter in /<Client>FacturaE/listado_facturas_ficha.jsp is not properly sanitized, allowing injection of malicious JavaScript through a crafted URL.

MitigationUpgrade to Quiter Gateway version 4.7.0 or later. Until then, implement input validation and output encoding for the id_factura parameter to neutralize malicious script payloads.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed Quiter Gateway version
    Locate the Quiter Gateway installation directory and check for version information in build files, configuration files, or the application metadata (such as MANIFEST.MF, version.properties, or the admin interface). Compare the version number to 4.7.0.
    Affected if The installed version is any version prior to 4.7.0 (e.g., 4.6.x, 4.5.x, earlier).
  2. Verify the vulnerable JSP endpoint exists
    Check the web application deployment directory for the path /<Client>FacturaE/listado_facturas_ficha.jsp. The <Client> portion is a placeholder; search for any directory matching *FacturaE pattern containing listado_facturas_ficha.jsp.
    Affected if The file listado_facturas_ficha.jsp exists in a *FacturaE directory under the webapp root.
  3. Test id_factura parameter for reflected XSS
    Send a crafted HTTP request to the endpoint with a benign XSS payload in the id_factura parameter (e.g., id_factura=<script>alert(1)</script>) and inspect the response to see if the script tags are returned unescaped in the HTML output.
    Affected if The response contains the raw id_factura parameter value unencoded or unsanitized within the HTML page (script tags appear as literal text in the response body).

You are affected if Quiter Gateway version is below 4.7.0 AND the listado_facturas_ficha.jsp endpoint is accessible AND the id_factura parameter reflects input without HTML encoding.

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 then, implement input validation and output encoding for the id_factura parameter to neutralize malicious script payloads.

Recommended fix High confidence

4.7.0

  1. Backup the current Quiter Gateway installation and database before proceeding with the upgrade
  2. Download Quiter Gateway version 4.7.0 from the official vendor (Quiter)
  3. Upgrade the Quiter Gateway installation to version 4.7.0 following the vendor's standard upgrade procedure
  4. After upgrade, verify the fix by testing that the id_factura parameter in /<Client>FacturaE/listado_facturas_ficha.jsp no longer accepts malicious JavaScript payloads
  5. Confirm the application is functioning correctly post-upgrade
Caveat Review Quiter Gateway 4.7.0 release notes for any configuration or compatibility changes before upgrading

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

Fix this in Quiter Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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