Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-94 (对生成代码的控制不恰当(代码注入)) — Vulnerability Class 1636

1636 vulnerabilities classified as CWE-94 (对生成代码的控制不恰当(代码注入)). AI Chinese analysis included.

CWE-94 represents a critical code injection weakness where software constructs executable code using untrusted input without proper sanitization. Attackers typically exploit this vulnerability by injecting malicious scripts or commands into user-supplied fields, such as web forms or API parameters, which the application then executes directly. This allows adversaries to bypass security controls, steal sensitive data, or gain unauthorized administrative access to the underlying system. To prevent such exploits, developers must rigorously validate and sanitize all external inputs, ensuring that only expected characters are processed. Implementing strict allow-listing strategies, utilizing parameterized queries for database interactions, and avoiding dynamic code execution functions like eval() are essential defensive measures. By treating all user input as potentially hostile and applying robust encoding techniques, organizations can effectively neutralize injection vectors and maintain application integrity.

MITRE CWE Description
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.
Common Consequences (4)
Access ControlBypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access ControlGain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can…
Non-RepudiationHide Activities
Often the actions performed by injected control code are unlogged.
Mitigations (5)
Architecture and DesignRefactor your program so that you do not have to dynamically generate code.
Architecture and DesignRun your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating s…
ImplementationAssume 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…
TestingUse dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
OperationRun the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Examples (2)
This example attempts to write user messages to a message file and allow users to view them.
$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); }
Bad · PHP
name=h4x0r message=%3C?php%20system(%22/bin/ls%20-l%22);?%3E
Attack
edit-config.pl: This CGI script is used to modify settings in a configuration file.
use CGI qw(:standard); sub config_file_add_key { my ($fname, $key, $arg) = @_; # code to add a field/key to a file goes here } sub config_file_set_key { my ($fname, $key, $arg) = @_; # code to set key to a particular file goes here } sub config_file_delete_key { my ($fname, $key, $arg) = @_; # code to delete key from a particular file goes here } sub handleConfigAction { my ($fname, $action) = @_; my $key = param('key'); my $val = param('val'); # this is super-efficient code, especially if you have to invoke # any one of dozens of different functions! my $code = "config_file_$action_key(\$fnam
Bad · Perl
add_key(",","); system("/bin/ls");
Attack
CVE IDTitleCVSSSeverityPublished
CVE-2026-46409 OpenYak local API: unauthenticated CSRF chain leads to Remote Code Execution — openyak 9.6 Critical2026-08-07
CVE-2026-17603 Nexus Repository 3 - HikariCP connectionInitSql Injection RCE via DataStore Configuration API — Nexus Repository 3 8.7 High2026-08-07
CVE-2026-48054 OpenZeppelin Contracts Wizard has Code Injection in Generated Hardhat and Foundry Tests via Unsanitized opts.name / opts.uri — contracts-wizard 8.8 High2026-08-06
CVE-2026-45572 Decidim: HTML content blocks allow stored script execution — decidim 4.8 Medium2026-08-06
CVE-2026-50159 Mermaid allows CSS injection applying to sibling elements of the diagram — mermaid 5.3 Medium2026-08-06
CVE-2026-19060 FoundationAgents MetaGPT code injection — MetaGPT 5.3 Medium2026-08-06
CVE-2026-19058 FoundationAgents MetaGPT data_interpreter.py DataInterpreter code injection — MetaGPT 5.3 Medium2026-08-06
CVE-2026-66709 WordPress CTX Feed plugin <= 6.6.42 - Remote Code Execution (RCE) vulnerability — CTX Feed 9.1 Critical2026-08-06
CVE-2026-65553 WordPress Spider Analyser – WordPress搜索引擎蜘蛛分析插件 plugin <= 2.1.3 - Remote Code Execution (RCE) vulnerability — Spider Analyser &#8211; WordPress搜索引擎蜘蛛分析插件 10.0 Critical2026-08-06
CVE-2026-65548 WordPress Betheme theme <= 28.4.2 - Remote Code Execution (RCE) vulnerability — Betheme 9.9 Critical2026-08-06
CVE-2026-67531 FrontMCP: CodeCall sandbox escape -> host RCE via live Zod schema exposure by getTool — frontmcp 9.3 Critical2026-08-05
CVE-2026-71319 Nuxt.js Unauthenticated WebSocket RPC Call Leading to Remote Code Execution — devtools 9.6 Critical2026-08-05
CVE-2026-55522 PraisonAI workflow include bypasses tools.py autoload opt-in and executes included recipe code — PraisonAI 7.8 High2026-08-05
CVE-2026-17624 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.5 High2026-08-05
CVE-2026-17633 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.5 High2026-08-05
CVE-2026-17632 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.8 High2026-08-05
CVE-2026-9196 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.1 High2026-08-05
CVE-2026-8182 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.8 High2026-08-05
CVE-2026-8478 Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling — Langflow OSS 8.8 High2026-08-05
CVE-2026-70609 Electron: DevTools JavaScript Injection via Unsanitized Dock State Parameter — electron 5.7 Medium2026-08-05
CVE-2026-71278 rust-iot-platform Unauthenticated Remote Code Execution via Unsandboxed Calc-Rule Script Evaluation — rust-iot-platform 9.8 Critical2026-08-05
CVE-2026-71235 Magistrala IoT Platform: Unrestricted Go/Lua Script Execution in Rules Engine — magistrala 8.8 High2026-08-05
CVE-2026-71232 MacCMS10: Incomplete Function Blacklist in Template Editor Enables Authenticated RCE — maccms10 7.2 High2026-08-05
CVE-2026-70553 MaxSite CMS Unauthenticated RCE via Install Endpoint — MaxSite CMS 9.8 Critical2026-08-04
CVE-2026-70477 Flowise: CSV Agent Prompt Injection Remote Code Execution Vulnerability — Flowise 9.5 Critical2026-08-04
CVE-2026-69264 Flowise: RCE via CSVAgent csvFile data URI base64 segment is interpolated into Python source without validation — Flowise 9.4 Critical2026-08-04
CVE-2026-69259 Flowise RCE via SQLite Record Manager Node — Flowise 9.4 Critical2026-08-04
CVE-2026-64633 Veeam ONE 代码注入漏洞 — ONE 10.0 Critical2026-08-04
CVE-2026-58074 Veeam ONE 代码注入漏洞 — ONE 8.6 High2026-08-04
CVE-2026-69256 Flowise: Remote Code Execution Vulnerability in CSVAgent — Flowise 9.4 Critical2026-08-04

Vulnerabilities classified as CWE-94 (对生成代码的控制不恰当(代码注入)) represent 1636 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.