CVE-2024-32406: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 2024.1 : patch affected systems soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2024.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Apr 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-26.
What to do
AI-suggested
1. Upgrade to inducer relate version 2024.1 or later as soon as the patch is available to eliminate the vulnerability. 2. Until patching is possible, restrict network access to the Batch-Issue Exam Tickets function, limiting it to trusted internal users and systems only. 3. Implement strict input validation and sanitization on all inputs processed by the template engine to prevent injection of malicious payloads. 4. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting template injection patterns. 5. Conduct thorough code reviews and security testing focusing on template usage and input handling in the affected function. 6. Monitor logs and network traffic for unusual activity related to the batch ticket issuance process, including unexpected template syntax or command execution attempts. 7. Educate developers and administrators about SSTI risks and secure coding practices to prevent similar vulnerabilities. 8. Consider deploying runtime application self-protection (RASP) tools to detect and block exploitation attempts in real time. 9. Maintain an incident response plan tailored to potential exploitation scenarios involving remote code execution.
Description
Server-Side Template Injection (SSTI) vulnerability in inducer relate before v.2024.1 allows a remote attacker to execute arbitrary code via a crafted payload to the Batch-Issue Exam Tickets function.