{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50477 exists.","fix":"No fix has been published for CVE-2025-50477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50477 is a medium-severity vulnerability in n/a, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-50477 and fix it if it is affected.\n\nWhat it is: CVE-2025-50477 is a medium-severity vulnerability in n/a, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50477 exists.\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-50477/ (Markdown: https://insights.sbomify.com/CVE-2025-50477/index.md)","id":"CVE-2025-50477","markdown":"https://insights.sbomify.com/CVE-2025-50477/index.md","name":"CVE-2025-50477","record":{"aliases":["GHSA-4jf4-wr6q-827p"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LBRY desktop client","requires_auth":"none","summary":"Attackers can redirect LBRY desktop users to malicious pages via URL redirection, potentially facilitating phishing attacks.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"A URL redirection in lbry-desktop v0.53.9 allows attackers to redirect victim users to attacker-controlled pages.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Open redirect in n/a","id":"CVE-2025-50477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Mezzanine CMS vulnerable to Cross-site Scripting","id":"CVE-2025-50481"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-50475"},"products":["n/a"],"published":"2025-07-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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-23","vendors":["n/a"]},"summary":"Attackers can redirect LBRY desktop users to malicious pages via URL redirection, potentially facilitating phishing attacks.","url":"https://insights.sbomify.com/CVE-2025-50477/"}