dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-45307

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Speakr is a personal, self-hosted web application designed for transcribing audio recordings. Prior to 0.8.20-alpha, the is_safe_url() helper used to validate post-login redirect targets applied urljoin(request.host_url, target) before parsing, while the controller passed the raw target to redirect(). A scheme-relative input such as ////evil.com resolved to a same-host URL during validation but was emitted verbatim in the Location header, where the browser interpreted it as a network-path-relative redirect to an attacker-controlled host. This vulnerability is fixed in 0.8.20-alpha.

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 · high confidence

This is an Open Redirect vulnerability in Speakr's login redirect functionality. The is_safe_url() helper used urljoin() to resolve the target URL before validation, but the raw target was passed to redirect(), allowing scheme-relative inputs like '////evil.com' to pass validation as same-host but emit as a network-path-relative redirect to an attacker-controlled host in the Location header.

MitigationUpgrade to Speakr version 0.8.20-alpha or later, which fixes the URL validation to properly parse and validate the redirect target before emitting it in the Location header.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Speakr installation and version
    Check the source code for a version file, composer.json, or version constant. Common paths include root directory files like VERSION, composer.json, or a config/version.php
    Affected if Installed version is below 0.8.20-alpha (the fixed version)
  2. Locate is_safe_url() helper function
    Search the codebase for the is_safe_url() function definition, typically in a helpers or utils file
    Affected if The function exists and uses urljoin() before performing validation checks
  3. Examine redirect() calls in login flow
    Search for redirect() function calls that handle the 'next' or 'redirect' query parameter, typically in authentication controllers
    Affected if The redirect target is passed to redirect() without sanitization after is_safe_url() validation
  4. Test for scheme-relative URL bypass
    If you have access to the login page, submit a redirect URL like '////evil.com' or '//evil.com' in the 'next' or 'redirect' parameter
    Affected if The application redirects to an external domain instead of rejecting or staying on the same host
  5. Verify Location header behavior
    Inspect the HTTP response headers when a scheme-relative URL is provided as redirect target
    Affected if The Location header contains a network-path-relative URL (starts with //) or absolute URL pointing to an attacker-controlled domain
  6. Check URL validation logic flow
    Review the code flow: input -> is_safe_url() -> redirect(). Confirm if urljoin() resolves the URL before validation but the original raw input is used in redirect()
    Affected if The code uses urljoin() to test validity but passes the unmodified user input to redirect(), creating a mismatch between validation and actual redirect behavior

A user is affected if they run Speakr version below 0.8.20-alpha AND the application uses the vulnerable redirect pattern with user-controlled redirect parameters in the login flow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Speakr version 0.8.20-alpha or later, which fixes the URL validation to properly parse and validate the redirect target before emitting it in the Location header.

Recommended fix Moderate confidence

0.8.20-alpha

  1. Backup your current Speakr installation and database
  2. Upgrade Speakr to version 0.8.20-alpha or later
  3. Verify the upgrade was successful by checking the application version
  4. Test that legitimate post-login redirects function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45307 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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