Software weaknesses, explained simply
CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.
CWE-94 · Improper Control of Generation of Code
Untrusted data can become executable code.
Headline signal
CWE-94 · Improper Control of Generation of Code
Untrusted data can become executable code.
In plain English
Untrusted data can become executable code.
What this can look like
A feature evaluates attacker-controlled content as code, allowing the attacker to run logic that the developer never intended.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.