{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-8663 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8663 is a high-severity vulnerability in upKeeper Manager, published on 3 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-8663 and fix it if it is affected.\n\nWhat it is: CVE-2025-8663 is a high-severity vulnerability in upKeeper Manager, published on 3 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-8663 in the wild and no public exploit code.\n\nAffected product: upKeeper Manager. 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-8663/ (Markdown: https://insights.sbomify.com/CVE-2025-8663/index.md)","id":"CVE-2025-8663","markdown":"https://insights.sbomify.com/CVE-2025-8663/index.md","name":"CVE-2025-8663","record":{"aliases":["GHSA-fpqq-xvp5-hhmq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"low_privilege","summary":"Attackers can read sensitive credentials from log files in upKeeper Manager, potentially leading to account takeover.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"upKeeper","cpe":[{"product":"upkeeper_manager","vendor":"upkeeper"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Insertion of Sensitive Information into Log File vulnerability in upKeeper Solutions upKeeper Manager allows Use of Known Domain Credentials.This issue affects upKeeper Manager: from 5.0.0 before 5.2.12.","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":"Information disclosure in upKeeper Manager","id":"CVE-2025-8663","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":"XSS in Saysis Computer Systems' StarCities","id":"CVE-2025-8664"},"packages":[],"prev":{"headline":"Other in OpenAM","id":"CVE-2025-8662"},"products":["upKeeper Manager"],"published":"2025-09-03","related":[{"cvss_score":10,"headline":"Bypass multifactor authentication","id":"CVE-2024-42462","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":9.5,"headline":"Lack of resources and rate limiting - login","id":"CVE-2024-42466","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":9,"headline":"Lack of resources and rate limiting - two factor authentication","id":"CVE-2024-42465","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":8.6,"headline":"Leak of organizations messages","id":"CVE-2024-42463","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":7.6,"headline":"Leak of user information","id":"CVE-2024-42464","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":7.3,"headline":"Information disclosure in upKeeper Manager","id":"CVE-2025-11446","kev_date_added":null,"published":"2025-11-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-03","vendors":["upKeeper Solutions"]},"summary":"Attackers can read sensitive credentials from log files in upKeeper Manager, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2025-8663/"}