CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')

Base

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.

Consequences

Confidentiality: Read Files or Directories, Read Application Data
Access Control: Bypass Protection Mechanism
Access Control: Gain Privileges or Assume Identity
Integrity, Confidentiality, Availability, Other: Execute Unauthorized Code or Commands
Non-Repudiation: Hide Activities

How to prevent it

Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
Implementation: Perform proper output validation and escaping to neutralize all code syntax from data written to code files.

Recent advisories

CVE-2026-86218 — N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.
GHSA-wcg9-pgqv-xm5v — XWiki Platform allows XSS through XClass name in string properties
GHSA-w7w4-qjgg-372x — Froxlor contains Static Code Injection
GHSA-x28w-hvwc-mp75 — Static Code Injection in Microweber

All advisories for CWE-96

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor