dbcve.org
Quiter GatewayApplication · Quiter

CVE-2025-40720

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

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 campo parameter in /<Client>FacturaE/VerFacturaPDF.

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 Cross-site Scripting (XSS) vulnerability in the campo parameter of the /<Client>FacturaE/VerFacturaPDF endpoint in Quiter Gateway versions prior to 4.7.0. An attacker can craft a malicious URL containing JavaScript payload in the campo parameter, which gets reflected back and executed in the victim's browser when they click the link.

MitigationUpgrade to Quiter Gateway version 4.7.0 or later, which contains the security fix. As a compensating control, implement proper input validation and output encoding on the campo parameter before rendering any user-supplied content.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Quiter Gateway installation
    Identify if Quiter Gateway is installed in your environment by checking for the Quiter Gateway application, service, or documentation.
    Affected if Quiter Gateway is not installed, this CVE does not apply.
  2. Find installed version
    Locate the version of Quiter Gateway running in your environment. Check the application startup logs, version info endpoint, or configuration files for the version number.
    Affected if You cannot determine the version or the version is below 4.7.0.
  3. Check endpoint accessibility
    Verify if the /<Client>FacturaE/VerFacturaPDF endpoint is accessible in your Quiter Gateway installation. This is the vulnerable endpoint that accepts the campo parameter.
    Affected if The endpoint is exposed and your version is below 4.7.0.
  4. Compare version against affected range
    Compare your identified Quiter Gateway version to the affected range: versions prior to 4.7.0. Versions 4.7.0 and later are not affected.
    Affected if Your installed version is less than 4.7.0 and the vulnerable endpoint is accessible.

You are affected if Quiter Gateway is installed, the /<Client>FacturaE/VerFacturaPDF endpoint is accessible, and the installed version is below 4.7.0.

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, which contains the security fix. As a compensating control, implement proper input validation and output encoding on the campo parameter before rendering any user-supplied content.

Recommended fix Moderate confidence

Quiter Gateway 4.7.0

  1. Contact Quiter support or consult official Quiter documentation to obtain the Quiter Gateway 4.7.0 upgrade package
  2. Review Quiter Gateway upgrade documentation for proper upgrade procedures
  3. Backup the current Quiter Gateway configuration and data
  4. Execute the upgrade process according to Quiter's official upgrade guide
  5. After upgrade, verify that the /<Client>FacturaE/VerFacturaPDF endpoint properly sanitizes the campo parameter
  6. Confirm the XSS vulnerability is no longer exploitable by testing with a benign payload in the campo parameter

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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