CVE-2025-40616
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 · uneditedReflected Cross-Site Scripting (XSS) vulnerability in Bookgy. This vulnerability allows an attacker to execute JavaScript code in the victim's browser by sending a malicious URL through the "IDRESERVA" parameter in /bkg_imprimir_comprobante.php.
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 confidenceReflected XSS in Bookgy's /bkg_imprimir_comprobante.php allows script execution via the IDRESERVA parameter. The vulnerability is medium severity due to its reflected nature, requiring user interaction (clicking a malicious link).
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Bookgy installation directorySearch for the file bkg_imprimir_comprobante.php in your web server's document root or application directories. Common paths include /var/www/html/, /www/, or your web application's root folder.Affected if The file exists in your environment, indicating Bookgy is installed.
-
Inspect the vulnerable PHP fileOpen bkg_imprimir_comprobante.php and locate the code that handles the IDRESERVA parameter. Look for any $_GET or $_REQUEST usage of 'IDRESERVA' without sanitization functions such as htmlspecialchars, htmlentities, or input validation.Affected if The file contains direct use of the IDRESERVA parameter without output encoding or input validation.
-
Verify lack of output encodingCheck if the IDRESERVA value is echoed or printed back to the user without being passed through encoding functions. Look for patterns like echo $_GET['IDRESERVA'] or similar without htmlspecialchars().Affected if The parameter value is reflected in the response without proper HTML encoding.
-
Confirm parameter is accessible via URLAttempt to access the page with a test IDRESERVA value (for example, bkg_imprimir_comprobante.php?IDRESERVA=test) and verify the value appears in the rendered page output.Affected if The parameter value is reflected in the page output, making XSS exploitation possible.
If Bookgy is installed and the bkg_imprimir_comprobante.php file reflects the IDRESERVA parameter without sanitization or encoding, your environment is affected by this reflected XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement proper input validation and output encoding on the IDRESERVA parameter in the affected PHP file. Use context-aware escaping and consider implementing a Content Security Policy.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-40616 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-40616 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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