CVE-2024-53556: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2024-53556, organizations should implement strict validation and sanitization of the 'next' parameter on the /login endpoint to ensure redirection only occurs to internal, trusted URLs. This can be achieved by maintaining a whitelist of allowed redirect destinations or by rejecting any external URLs outright. Additionally, deploying web application firewalls (WAFs) with rules to detect and block suspicious redirect patterns can help reduce risk. User education is critical: training users to recognize suspicious URLs and avoid clicking on unexpected login links can prevent exploitation. Monitoring logs for unusual redirect attempts or spikes in login URL access can provide early detection of exploitation attempts. Until an official patch is released, consider temporarily disabling or restricting the use of the 'next' parameter if feasible. Finally, keep abreast of updates from Taiga developers and apply security patches promptly once available.
Description
An Open Redirect vulnerability in Taiga v6.8.1 allows attackers to redirect users to arbitrary websites via appending a crafted link to /login?next= in the login page URL.