{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-61132 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-61132 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61132 is a high-severity vulnerability in n/a, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61132 and fix it if it is affected.\n\nWhat it is: CVE-2025-61132 is a high-severity vulnerability in n/a, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-61132 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-61132/ (Markdown: https://insights.sbomify.com/CVE-2025-61132/index.md)","id":"CVE-2025-61132","markdown":"https://insights.sbomify.com/CVE-2025-61132/index.md","name":"CVE-2025-61132","record":{"aliases":["GHSA-vr7m-2734-5h7w"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Braindump web app","requires_auth":"low_privilege","summary":"Attackers can poison password reset links via Host header injection in Braindump, leading to account takeover if SERVER_NAME is not fixed.","user_interaction":"not_required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-620","name":"Unverified Password Change"}],"description":"A Host Header Injection vulnerability in the password reset component in levlaz braindump v0.4.14 allows remote attackers to conduct password reset poisoning and account takeover via manipulation of the Host header when Flask's url_for(_external=True) generates reset links without a fixed SERVER_NAME.","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":"Open redirect in n/a","id":"CVE-2025-61132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Open redirect in n/a","id":"CVE-2025-61136"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-61128"},"products":["n/a"],"published":"2025-10-23","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-23","vendors":["n/a"]},"summary":"Attackers can poison password reset links via Host header injection in Braindump, leading to account takeover if SERVER_NAME is not fixed.","url":"https://insights.sbomify.com/CVE-2025-61132/"}