CVE-2025-50477
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA URL redirection in lbry-desktop v0.53.9 allows attackers to redirect victim users to attacker-controlled pages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencelbry-desktop v0.53.9 contains an open redirect vulnerability where attackers can craft malicious URLs to redirect victim users to attacker-controlled external websites. This can facilitate phishing attacks by tricking users into believing they are navigating to legitimate pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if lbry-desktop is installedOn Windows, check C:\Program Files\LBRY\resources\app\package.json or look for LBRY in Programs and Features. On macOS, check /Applications/LBRY.app/Contents/Resources/app/package.json or run 'ls /Applications | grep -i lbry'. On Linux, check /opt/lbry/resources/app/package.json or look in your package manager.Affected if lbry-desktop is not installed on the system
-
Determine the installed version of lbry-desktopOpen the package.json file in the lbry-desktop installation directory (as identified in step 1) and locate the 'version' field. Alternatively, run the application and look for the version number in the Help > About menu, or run 'lbry-desktop --version' from command line if available.Affected if The version listed is 0.53.9 exactly, or falls within a range starting at 0.53.9 with no fixed upper bound (indicating an unpatched version)
-
Identify if URL redirect functionality existsSearch the application's source code (if accessible) or configuration files for redirect-related endpoints or functions. Common patterns include: 'redirect', 'openExternal', 'shell.openExternal', URL parameters named 'url', 'redirect', 'next', or 'dest'. Check the main process JavaScript files in the resources/app folder.Affected if URL redirect or external link opening functionality is present and uses unsanitized user-supplied input
-
Test for vulnerable redirect behaviorIf you can access the application, observe the behavior when clicking links or navigating. Note whether the application opens external URLs directly without validation. Check if there are any URL validation functions present in the codebase that whitelist only internal domains.Affected if The application redirects to arbitrary external URLs without strict domain whitelisting or validation
A user is affected if lbry-desktop version 0.53.9 is installed and the application contains redirect functionality that allows unsanitized external URLs to be used as redirect destinations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL validation ensuring all redirect destinations point to trusted, internal domains. If a patched version is available, upgrade to the fixed release.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50477 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data