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

Code Examples & CVEs

Demonstrative Examples

This example attempts to write user messages to a message file and allow users to view them.

While the programmer intends for the MessageFile to only include data, an attacker can provide a message such as:

BadPHP

$MessageFile = "messages.out";if ($_GET["action"] == "NewMessage") {$name = $_GET["name"];$message = $_GET["message"];$handle = fopen($MessageFile, "a+");fwrite($handle, "<b>$name</b> says '$message'<hr>\n");fclose($handle);echo "Message Saved!<p>\n";}else if ($_GET["action"] == "ViewMessages") {include($MessageFile);}

Observed CVE Examples (5)

CVE-2002-0495

Perl code directly injected into CGI library file from parameters to another CGI program.

View Details

CVE-2005-1876

Direct PHP code injection into supporting template file.

View Details

CVE-2005-1894

Direct code injection into PHP script that can be accessed by attacker.

View Details

CVE-2003-0395

PHP code from User-Agent HTTP header directly inserted into log file implemented as PHP script.

View Details

CVE-2007-6652

chain: execution after redirect allows non-administrator to perform static code injection.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-96 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-96, Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Input Validation controls for Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')

MITRE associates mitigation with Implementation; the listed strategies include Input Validation, and Output Encoding; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-96 into implementation, review, and verification checks for the affected component.

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

Triage CWE-96 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-96, Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-96

Apply MITRE's full root-cause mapping guidance when using CWE-96, Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-96 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-96, Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

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

CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')?+

If exploited, CWE-96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')) it can compromise Confidentiality, Access Control, Integrity, Availability, Other and Non-Repudiation, leading to outcomes such as Read Files or Directories, Read Application Data, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands and Hide Activities.

How do you prevent or mitigate Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')?+

Recommended mitigations for CWE-96 include: Perform proper output validation and escaping to neutralize all code syntax from data written to code files.

Which programming languages are affected by Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')?+

CWE-96 commonly affects PHP, Perl and Interpreted. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')?+

MITRE documents real CVEs mapped to CWE-96, including CVE-2002-0495, CVE-2005-1876, CVE-2005-1894, CVE-2003-0395 and CVE-2007-6652. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-96 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

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

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Scope

Impact

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Strategy

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (5)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-96 with SSDF evidence

Apply Input Validation controls for Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')

Triage CWE-96 against known exploitation evidence

Apply precise root-cause mapping to CWE-96

Validate CWE-96 with root-cause mapping checks

Frequently Asked Questions

Learn More