Open Redirect Vulnerability in Taguette
CVE-2025-67502GHSA-5923-r76v-mprm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (taguette 1.5.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI taguette
- Affected
- <= 1.5.1
- Fixed in
- 1.5.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5923-r76v-mprm lists affected ranges: PyPI taguette >=0 <1.5.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5923-r76v-mprm lists affected ranges: PyPI taguette >=0 <=1.5.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
- EPSS
- CVE-2025-67502: 0.26% estimated exploitation activity in the next 30 days; percentile 18.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An Open Redirect vulnerability exists in Taguette that allows attackers to craft malicious URLs that redirect users to arbitrary external websites after authentication. This can be exploited for phishing attacks where victims believe they are interacting with a trusted Taguette instance but are redirected to a malicious site designed to steal credentials or deliver malware. Severity: Medium to High --- Details The application accepts a user-controlled next parameter and uses it directly in HTTP redirects without any validation. The vulnerable code is located in two places: Location 1: Login Handler (taguette/web/views.py, lines 140-144) This method is called after successful login (line 132) and when an already-logged-in user visits the login page (line 109). Location 2: Cookies Prompt Handler (taguette/web/views.py, lines 79-85) In both cases, if next is provided by the user, it is passed directly to self.redirect() without checking whether it points to the same host or is a…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-5923-r76v-mprm
- Revision 1 · created ·
Published from osv record GHSA-5923-r76v-mprm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-67502 Advisory: Open Redirect Vulnerability in Taguette IDs: CVE-2025-67502, GHSA-5923-r76v-mprm Record: https://patchnext.com/advisories/cve-2025-67502 (revision 2, source checked 26 Oct 2026, 13:36 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: taguette 1.5.2. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI taguette: affected <= 1.5.1; fixed in 1.5.2 ## Suggested inspection (read-only) - `python -m pip show taguette`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on taguette. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-5923-r76v-mprm (OSV record GHSA-5923-r76v-mprm lists affected ranges: PyPI taguette >=0 <1.5.2 (fixed)) - Verified: https://github.com/advisories/GHSA-5923-r76v-mprm (GitHub-reviewed advisory GHSA-5923-r76v-mprm lists affected ranges: PyPI taguette >=0 <=1.5.1) Commands are suggestions: review each one before running it.
Loading voting…