CVE-2025-40617
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 "IDTIPO", "IDPISTA" and "IDSOCIO" parameters in /bkg_seleccionar_hora_ajax.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 confidenceSQL injection vulnerability in Bookgy's /bkg_seleccionar_hora_ajax.php allows remote attackers to execute arbitrary SQL commands via the IDTIPO, IDPISTA, and IDSOCIO parameters. Successful exploitation grants full database access including read, write, update, and delete capabilities.
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.
-
Locate the vulnerable PHP fileSearch the web server's document root for the file /bkg_seleccionar_hora_ajax.php. Common paths include /var/www/html/, /var/www/, or the application's web root directory. Use: find /var/www -name 'bkg_seleccionar_hora_ajax.php' 2>/dev/nullAffected if The file exists in the web application directory
-
Identify parameter exposureReview the application's HTTP endpoints and determine if the IDTIPO, IDPISTA, or IDSOCIO parameters are accepted via GET or POST requests to the vulnerable file. Check web server logs or proxy records for requests to this endpoint.Affected if The application accepts and processes IDTIPO, IDPISTA, or IDSOCIO parameters without proper input handling
-
Check for dynamic SQL usageExamine the source code of bkg_seleccionar_hora_ajax.php (if accessible) and look for SQL query construction that directly incorporates the IDTIPO, IDPISTA, or IDSOCIO parameters into query strings without using prepared statements or parameter binding.Affected if The code builds SQL queries by concatenating or interpolating these parameters directly into query strings
-
Verify external accessibilityConfirm whether the web application is accessible from external networks or untrusted environments. Test accessing the file URL (e.g., https://yourdomain.com/bkg_seleccionar_hora_ajax.php) and attempting to submit the vulnerable parameters.Affected if The endpoint is reachable from untrusted networks and accepts user-supplied input for the affected parameters
If the file /bkg_seleccionar_hora_ajax.php exists in the web root and accepts IDTIPO, IDPISTA, or IDSOCIO parameters without parameterized queries, the environment is affected by this SQL injection 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 prepared statements/parameterized queries for all database queries using these parameters, and apply input validation/encoding. Conduct a broader code audit to identify and remediate similar SQL injection vulnerabilities throughout the application.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40617 — 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-40617 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