CVE-2024-37621: strongshop · Template Injection
Affects strongshopSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhebing123/strongshoppkg:github/hebing123/strongshopOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-37621, organizations should first verify if they are running StrongShop v1.0 and specifically assess the /shippingOptionConfig/index.blade.php component. Immediate steps include restricting access to this component to only trusted, authenticated users with necessary privileges. Implement strict input validation and sanitization to prevent malicious template code injection. Employ web application firewalls (WAFs) with custom rules to detect and block SSTI attack patterns. Monitor server logs and application behavior for unusual activity indicative of exploitation attempts. If possible, isolate the affected application environment to limit lateral movement in case of compromise. Since no official patches are currently available, consider applying temporary mitigations such as disabling template rendering features that process user input or using safer templating engines. Regularly update credentials and enforce strong authentication mechanisms to reduce the risk of privilege escalation. Stay alert for vendor updates or patches addressing this vulnerability and apply them promptly once released.
Description
StrongShop v1.0 was discovered to contain a Server-Side Template Injection (SSTI) vulnerability via the component /shippingOptionConfig/index.blade.php.