wp-email-templates
Warn
Audited by Gen Agent Trust Hub on Aug 22, 2026
Risk Level: MEDIUMREMOTE_CODE_EXECUTIONPROMPT_INJECTION
Full Analysis
- [DYNAMIC_EXECUTION]: The
render_templatehelper function inSKILL.mduses theincludestatement to load PHP files from a path computed at runtime ($dir . $template . '.php'). Similarly, theMy_Plugin_Emailclass inreferences/html-email-patterns.mdusesfile_get_contentson a provided path. This dynamic loading from computed paths is a security risk if the path or template name is not strictly validated against a whitelist. - [INDIRECT_PROMPT_INJECTION]: The skill facilitates the ingestion of external data via the
$varsarray, which is then interpolated into HTML email templates. While the skill recommends escaping output (e.g., usingesc_html), the use ofextract(EXTR_SKIP)and dynamic template rendering creates an attack surface for indirect injection. - Ingestion points: The
$varsparameter inrender_emailandrender_templatefunctions withinSKILL.md. - Boundary markers: Absent in the
render_templatewrapper, although standard WordPress escaping functions are used within individual template files. - Capability inventory: File system access via
include(SKILL.md) andfile_get_contents(references/html-email-patterns.md). - Sanitization: The skill correctly instructs developers to use WordPress escaping functions like
esc_html()andesc_url()for variable output.
Audit Metadata