Threadlinqs IntelligenceStart free

Weakness · BaseCWE-1336

CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine

KEV-linkedBase

As of 2026-11-19, CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine) underlies 19 CVEs tracked by Threadlinqs, 1 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 27 tracked threats.

CVEs
19Mapped to CWE-1336
CISA KEV
1Exploited in the wild
Critical
9CVSS v3 critical CVEs
Threats
27Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-1336?

The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

Many web applications use template engines that allow developers to insert externally-influenced values into free text or messages in order to generate a full web page, document, message, etc. Such engines include Twig, Jinja2, Pug, Java Server Pages, FreeMarker, Velocity, ColdFusion, Smarty, and many others - including PHP itself. Some CMS (Content Management Systems) also use templates. Template engines often have their own custom command or expression language. If an attacker can influence input into a template before it is processed, then the attacker can invoke arbitrary expressions, i.e. perform injection attacks. For example, in some template languages, an attacker could inject the expression "{{7*7}}" and determine if the output returns "49" instead. The syntax varies depending on the language. In some cases, XSS-style attacks can work, which can obscure the root cause if the developer does not closely investigate the root cause of the error. Template engines can be used on the server or client, so both "sides" could be affected by injection. The mechanisms of attack or the affected technologies might be different, but the mistake is fundamentally the same.

CWE-1336 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Java; Language: PHP; Language: Python; Language: JavaScript; Language: Interpreted; Operating_System: Not OS-Specific.

Source: MITRE CWE (CWE-1336 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Integrity — Execute Unauthorized Code or Commands

Source: MITRE CWE, common consequences.

How CWE-1336 is exploited in the wild

Threadlinqs maps 19 CVEs to CWE-1336, published between 2026-02-09 and 2026-11-16. 1 is listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild. By CVSS v3 severity the set splits into 9 critical, 5 high, 3 medium. The highest EPSS score in the set is 3.9% (CVE-2026-75650), the modelled probability of exploitation in the next 30 days. 27 tracked threats reference CWE-1336 directly or through a CVE it covers; the most recent is “CVE-2026-111559: Batflat (sruupl) template injection in /contact endpoint allows unauthenticated remote PHP code execution” (2026-11-17). Affected products concentrate in Adobe (3), GitLab (2), JetBrains (2), among 15 vendors in total.

Vulnerabilities (CVEs)

All 19 CVEs mapped to CWE-1336, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

27 tracked threats cite CWE-1336; the 25 most recent are listed.

Mitigations

  • Architecture and Design: Choose a template engine that offers a sandbox or restricted mode, or at least limits the power of any available expressions, function calls, or commands.
  • Implementation: Use the template engine's sandbox or restricted mode, if available.

Source: MITRE CWE, potential mitigations.

Detection methods (MITRE CWE)

  • Automated Static Analysis (effectiveness: High): Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.