{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40645 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40645 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40645 is a high-severity vulnerability in ViDay, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40645 and fix it if it is affected.\n\nWhat it is: CVE-2025-40645 is a high-severity vulnerability in ViDay, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40645 in the wild and no public exploit code.\n\nAffected product: ViDay. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40645/ (Markdown: https://insights.sbomify.com/CVE-2025-40645/index.md)","id":"CVE-2025-40645","markdown":"https://insights.sbomify.com/CVE-2025-40645/index.md","name":"CVE-2025-40645","record":{"aliases":["GHSA-h2hv-xmr8-g377"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Viday web application","requires_auth":"none","summary":"An unauthenticated attacker can obtain sensitive customer information by sending a crafted HTTP GET request to the clients API endpoint.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Exposure 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Exposure of sensitive information in Viday","id":"CVE-2025-40645","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Exposure of sensitive information in Viday","id":"CVE-2025-40646"},"packages":[],"prev":{"headline":"Reflected Cross-Site Scripting (XSS) in QRGen's Riftzilla","id":"CVE-2025-40644"},"products":["ViDay"],"published":"2025-10-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-02","vendors":["ViDay"]},"summary":"An unauthenticated attacker can obtain sensitive customer information by sending a crafted HTTP GET request to the clients API endpoint.","url":"https://insights.sbomify.com/CVE-2025-40645/"}