CVE-2025-40615
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 "TEXTO" parameter in /api/api_ajustes.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 · moderate confidenceReflected XSS vulnerability in Bookgy's /api/api_ajustes.php endpoint. The TEXTO parameter reflects user-supplied input back in the response without proper sanitization, allowing attackers to inject malicious JavaScript that executes in victims' browsers when they click crafted links.
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.
-
Identify Bookgy installationSearch for Bookgy application files on the server, typically found in web root directories (e.g., /var/www/html, /www, C:\inetpub\wwwroot). Look for directories named 'bookgy' or application files containing 'Bookgy' branding.Affected if Bookgy software is installed on the server
-
Locate vulnerable endpointNavigate to the /api subdirectory within the Bookgy installation and confirm the presence of the file api_ajustes.php.Affected if The file api_ajustes.php exists in the /api directory of the Bookgy installation
-
Inspect TEXTO parameter handlingOpen api_ajustes.php in a text editor or use 'grep' to search for the TEXTO parameter. Examine how the parameter is processed and returned in the response. Look for absence of htmlspecialchars, strip_tags, or other encoding functions.Affected if The TEXTO parameter is used in the response without sanitization or output encoding functions such as htmlspecialchars()
-
Verify reflection in HTTP responseSend a test request to /api/api_ajustes.php with a harmless test string in the TEXTO parameter (e.g., TEXTO=test123). Capture the HTTP response and confirm whether the exact input appears in the response body.Affected if The TEXTO parameter value is reflected verbatim in the response without encoding
A user is affected if Bookgy is installed, the api_ajustes.php endpoint exists, and the TEXTO parameter reflects user input without sanitization in the response.
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 input validation and output encoding for the TEXTO parameter in api_ajustes.php, using context-appropriate escaping functions to neutralize script execution attempts.
- 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-40615 — 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-40615 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