GHSA-5923-r76v-mprm is a medium-severity (CVSS 5.4) Open Redirect vulnerability in taguette. A fix is available for taguette — see the affected versions and patch details below.
Open Redirect Vulnerability in Taguette
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5923-r76v-mprm.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-5923-r76v-mprm plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
taguetteReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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)
def _go_to_next(self):
next_ = self.get_argument('next', '')
if not next_:
next_ = self.reverse_url('index')
return self.redirect(next_) # ← No validation of next_ parameter
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)
def post(self):
self.set_cookie('cookies_accepted', 'yes', dont_check=True)
next_ = self.get_argument('next', '')
if not next_:
next_ = self.reverse_url('index')
return self.redirect(next_) # ← No validation of next_ parameter
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 relative URL.
PoC
Simply replace [your-taguette-instance] with your Taguette server domain and test these URLs in your browser:
Test 1: Cookies Prompt Redirect
https://[your-taguette-instance]/cookies?next=https://google.com
- Open the URL above in your browser
- Click "Accept cookies" button
- Result: You are redirected to
https://google.com(external site)
Test 2: Login Redirect
https://[your-taguette-instance]/login?next=https://google.com
- Open the URL above in your browser
- Log in with valid credentials
- Result: You are redirected to
https://google.com(external site)
Test 3: Already Logged In Redirect
https://[your-taguette-instance]/login?next=https://google.com
- First, log in to Taguette normally
- Then open the URL above
- Result: You are immediately redirected to
https://google.com
Note: We use
google.comas a safe external site for testing. In a real attack, this would be a phishing site.
Impact
- Who is affected: All users of any Taguette instance running in multi-user mode
- Attack vector: Social engineering / phishing via crafted URLs
- Exploitability: Trivial - requires only crafting a URL with a malicious
nextparameter - Consequences:
- Credential theft through phishing
- Malware distribution
- Session hijacking
- Reputation damage to organizations running Taguette instances
The vulnerability is particularly dangerous because:
- The login page displayed is completely legitimate, building victim trust
- Users have just entered their credentials, making them more likely to enter them again on a fake "session expired" page
- The trusted domain in the URL makes the attack more convincing
Recommended Fix
Validate that the next parameter is either a relative URL or points to the same host before redirecting.
Example Fix
Add a validation function:
from urllib.parse import urlparse
def is_safe_url(url, host):
"""Check if URL is safe for redirect (relative or same host)."""
if not url:
return False
parsed = urlparse(url)
# Reject protocol-relative URLs (//evil.com)
if url.startswith('//'):
return False
# Allow relative URLs (no scheme and no netloc)
if not parsed.scheme and not parsed.netloc:
return True
# Allow same-host URLs
return parsed.netloc == host
Then update the vulnerable methods:
def _go_to_next(self):
next_ = self.get_argument('next', '')
if not next_ or not is_safe_url(next_, self.request.host):
next_ = self.reverse_url('index')
return self.redirect(next_)
Apply the same fix to the CookiesPrompt.post() method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | taguette | all versions | 1.5.2pip install --upgrade 'taguette==1.5.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for taguette, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update taguette to 1.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5923-r76v-mprm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5923-r76v-mprm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5923-r76v-mprm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5923-r76v-mprm in your dependencies?
O3 Security finds GHSA-5923-r76v-mprm across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.