S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Oct 8, 2024

CVE-2023-22621 Scanner

CVE-2023-22621 Scanner - Server Side Template Injection (SSTI) vulnerability in Strapi

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2k
Times Used
continuous scan runs
5.5k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2023-22621
7.2
CVSScritical
Exploitable remotely over the internet · no authentication required.

Strapi through 4.5.5 allows authenticated Server-Side Template Injection (SSTI) that can be exploited to execute arbitrary code on the server. A remote attacker with access to the Strapi admin panel can inject a crafted payload that executes code on the server into an email template that bypasses the validation checks that should prevent code execution.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
n/aby n/a
n/a
Updated Aug 19, 2026View on NVD →
Detail

The Strapi platform is commonly used by developers and content creators to manage content and build applications. It provides a powerful Content Management System (CMS) that is highly customizable and extensible. Strapi is widely used for its easy integration with modern front-end technologies. It offers features like API generation, media library, and user permission management, which makes it popular among developers who need a flexible and powerful CMS solution. It's adopted by small businesses to enterprise companies alike due to its scalable architecture and open-source nature, allowing users to tailor it to their specific needs. Strapi's API-first design also allows developers to create, manage, and expose content through APIs without administrative overhead.

Server Side Template Injection (SSTI) is a vulnerability that allows an attacker to inject malicious templates code into a server-side template processing engine, leading to remote code execution. This vulnerability occurs because the application fails to properly sanitize user inputs that are used in server-side template rendering. Once injected, the malicious payload can execute arbitrary code on the server, potentially compromising the entire system. In the context of Strapi, an authenticated user with admin panel access could exploit this by injecting a crafted payload into email templates. This would bypass validation checks and execute code on the server, which the admin should have control over but fails to enforce security measures properly.

The vulnerability in Strapi is particularly concerning as it resides in the email template configuration. Attackers can exploit this by crafting a malicious payload to be injected into the email template engine. Specifically, this occurs in the email confirmation or reset password templates, where arbitrary code execution can be triggered if the template content handling is not correctly sanitized. The injection leverage occurs due to process bindings within the template engine, which a remote attacker can manipulate to perform unauthorized actions. This could include spawning processes or injecting HTTP requests, providing a significant attack vector for remote code execution.

If exploited, Server Side Template Injection (SSTI) in Strapi could lead to several adverse impacts, including unauthorized access and complete control over the affected system by attackers. It may result in data breaches, loss of system integrity, and availability due to unauthorized manipulation of server-side components. Malicious actors could potentially execute destructive code causing a Denial of Service (DoS), data leakage, and even lateral movement across the network environment, leading to broader impacts. This could severely affect an organization's operations, reputation, and compliance with data protection regulations. Attackers may persist their access to create backdoors or manipulate email templates to further compromise user trust and security.

REFERENCES

Solution Advice
  • Update Strapi to the latest version where this vulnerability is fixed.
  • Implement strict validation and sanitation of user inputs, especially within template configurations.
  • Restrict access to Strapi admin panel to trusted users only, and enforce strong authentication methods.
  • Conduct regular security audits and scans to detect potential vulnerabilities proactively.
  • Educate development teams about secure coding practices to prevent injection vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.