CVE-2025-40645
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 · uneditedExposure of sensitive information in Viday. This vulnerability could allow an unauthenticated attacker to obtain sensitive information about customers by sending an HTTP GET request to “/api/reserva/web/clients” using the “phone” parameter.
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 confidenceViday exposes a sensitive information disclosure vulnerability in its REST API. The endpoint /api/reserva/web/clients accepts a phone parameter without requiring authentication, allowing any unauthenticated user to query and obtain customer PII including names, contact details, and potentially other sensitive reservation data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Viday installationSearch for Viday web application components, configuration files, or services running in your environment. Check web server logs, application directories, or deployment manifests for references to 'Viday' or the '/api/reserva/' path.Affected if Viday reservation system is deployed in your environment
-
Verify endpoint accessibilitySend an HTTP GET or POST request to https://[your-host]/api/reserva/web/clients without including any authentication headers, cookies, or tokens. Observe if the endpoint responds.Affected if The /api/reserva/web/clients endpoint is reachable and responds to unauthenticated requests
-
Test phone parameter exposureSend a request to /api/reserva/web/clients with a phone parameter (e.g., ?phone=1234567890 or in POST body) containing any test phone number. Examine the response for customer PII such as names, addresses, or reservation details.Affected if The endpoint returns customer names, contact information, or reservation data in the response without requiring authentication
-
Review API access controlsExamine the application's configuration, API gateway settings, or web server configuration for any authentication or authorization rules applied to /api/reserva/web/clients. Check if the endpoint is explicitly excluded from auth requirements.Affected if No authentication is required for the endpoint, or the endpoint is marked as publicly accessible in security configurations
Your environment is affected if the Viday application is running and the /api/reserva/web/clients endpoint is accessible without authentication, returning customer PII in response to phone parameter queries.
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 authentication and authorization checks on the /api/reserva/web/clients endpoint to ensure only authorized users can access customer data. Additionally, audit similar API endpoints for consistent security controls.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40645 — 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-40645 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