CVE-2025-40618
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 · uneditedSQL injection vulnerability in Bookgy. This vulnerability could allow an attacker to retrieve, create, update and delete databases by sending an HTTP request 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 confidenceA SQL injection vulnerability in Bookgy's /bkg_imprimir_comprobante.php script allows unauthenticated attackers to inject arbitrary SQL commands through the unsanitized IDRESERVA parameter. This enables full database compromise including unauthorized data retrieval, modification, and deletion.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bookgy installationSearch the web server filesystem for Bookgy application files or directories, typically found in web root paths like /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for Bookgy-specific files, configuration files, or the application's directory structure.Affected if Bookgy software is present on the server
-
Locate vulnerable scriptSearch for the file bkg_imprimir_comprobante.php in the web application directory structure. Use commands like: find /var/www -name 'bkg_imprimir_comprobante.php' or dir /s /b C:\*bkg_imprimir_comprobante.phpAffected if The file bkg_imprimir_comprobante.php exists in the web application
-
Verify IDRESERVA parameter handlingExamine the bkg_imprimir_comprobante.php source code and inspect how the IDRESERVA parameter is used in database queries. Search for direct string concatenation or lack of prepared statements when building SQL queries with this parameter.Affected if The IDRESERVA parameter is used directly in SQL queries without parameterized queries, prepared statements, or input sanitization
-
Test parameter for SQL injectionIf authorized and in a non-production environment, send a crafted HTTP request with SQL injection payload in the IDRESERVA parameter (e.g., IDRESERVA=1' OR '1'='1) and observe the application response for SQL error messages or unexpected data disclosure.Affected if The application returns SQL syntax errors or allows unauthorized data retrieval through the IDRESERVA parameter
A user is affected if Bookgy is installed, the bkg_imprimir_comprobante.php script exists, and the IDRESERVA parameter is used in SQL queries without parameterized statements or input validation.
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 parameterized queries/prepared statements for all database queries using the IDRESERVA parameter, apply strict input validation, and apply any vendor-supplied patches for Bookgy.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40618 — 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-40618 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