{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67806 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-67806 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67806 is a low-severity vulnerability in n/a, published on 1 Apr 2026. 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-67806 and fix it if it is affected.\n\nWhat it is: CVE-2025-67806 is a low-severity vulnerability in n/a, published on 1 Apr 2026. 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-67806 in the wild and no public exploit code.\n\nAffected product: n/a. 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-67806/ (Markdown: https://insights.sbomify.com/CVE-2025-67806/index.md)","id":"CVE-2025-67806","markdown":"https://insights.sbomify.com/CVE-2025-67806/index.md","name":"CVE-2025-67806","record":{"aliases":["GHSA-7h2g-p6hq-vh75"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sage DPW","requires_auth":"none","summary":"Attackers can enumerate valid usernames via distinct login responses, potentially aiding further attacks; administrators should enable the toggle to obscure this behavior.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sage_dpw","vendor":"sagedpw"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"The login mechanism of Sage DPW 2021_06_004 displays distinct responses for valid and invalid usernames, allowing enumeration of existing accounts in versions before 2021_06_000. On-premise administrators can toggle this behavior in newer versions.","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 n/a","id":"CVE-2025-67806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-67807"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-67805"},"products":["n/a"],"published":"2026-04-01","related":[{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2024-56883","kev_date_added":null,"published":"2025-02-18"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2025-51532","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-51531","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-26583","kev_date_added":null,"published":"2020-10-16"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-26584","kev_date_added":null,"published":"2020-10-16"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2025-67805","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2024-56882","kev_date_added":null,"published":"2025-02-18"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-05-10","vendors":["n/a"]},"summary":"Attackers can enumerate valid usernames via distinct login responses, potentially aiding further attacks; administrators should enable the toggle to obscure this behavior.","url":"https://insights.sbomify.com/CVE-2025-67806/"}