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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-116 (对输出编码和转义不恰当) — Vulnerability Class 128

128 vulnerabilities classified as CWE-116 (对输出编码和转义不恰当). AI Chinese analysis included.

CWE-116 represents a critical input validation weakness where software fails to properly encode or escape output data before transmitting it to another component. This oversight disrupts the intended message structure, allowing attackers to inject malicious commands or alter data semantics by exploiting the parsing ambiguity. Exploitation typically occurs when unescaped special characters are interpreted as control sequences rather than literal data, leading to severe consequences such as cross-site scripting, command injection, or protocol manipulation. To mitigate this risk, developers must strictly enforce context-aware encoding strategies, ensuring that all output is sanitized according to the specific receiving component’s parsing rules. Implementing robust escaping libraries and validating data boundaries before transmission are essential practices to preserve message integrity and prevent unauthorized command execution.

MITRE CWE Description
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead. Most products follow a certain protocol that uses structured messages for communication between components, such as queries or commands. These structured messages can contain raw data interspersed with metadata or control information. For example, "GET /index.html HTTP/1.1" is a structured message containing a command ("GET") with a single argument ("/index.html") and metadata about which protocol version is being used ("HTTP/1.1"). If an application uses attacker-supplied inputs to construct a structured message without properly encoding or escaping, then the attacker could insert special characters that will cause the data to be interpreted as control information or metadata. Consequently, the component that receives the output will perform the wrong operations, or otherwise interpret the data incorrectly.
Common Consequences (3)
IntegrityModify Application Data
The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.
Integrity, Confidentiality, Availability, Access ControlExecute Unauthorized Code or Commands
The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.
ConfidentialityBypass Protection Mechanism
The communications between components can be modified in unexpected ways. Unexpected commands can be executed, bypassing other security mechanisms. Incoming data can be misinterpreted.
Mitigations (5)
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. Alternately, use built-in functions, but consider using wrappers in case t…
Architecture and DesignIf available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. For example, stored procedures can enforce database query structure and reduce the likel…
Architecture and Design, ImplementationUnderstand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required e…
Architecture and DesignIn some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting…
Architecture and DesignUse input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
Examples (2)
This code displays an email address that was submitted as part of a form.
<% String email = request.getParameter("email"); %> ... Email Address: <%= email %>
Bad · JSP
Consider a chat application in which a front-end web application communicates with a back-end server. The back-end is legacy code that does not perform authentication or authorization, so the front-end must implement it. The chat protocol supports two commands, SAY and BAN, although only administrators can use the BAN command. Each argument must be separated by a single space. The raw inputs are U…
$inputString = readLineFromFileHandle($serverFH); # generate an array of strings separated by the "|" character. @commands = split(/\|/, $inputString); foreach $cmd (@commands) { # separate the operator from its arguments based on a single whitespace ($operator, $args) = split(/ /, $cmd, 2); $args = UrlDecode($args); if ($operator eq "BAN") { ExecuteBan($args); } elsif ($operator eq "SAY") { ExecuteSay($args); } }
Bad · Perl
$inputString = GetUntrustedArgument("command"); ($cmd, $argstr) = split(/\s+/, $inputString, 2); # removes extra whitespace and also changes CRLF's to spaces $argstr =~ s/\s+/ /gs; $argstr = UrlEncode($argstr); if (($cmd eq "BAN") && (! IsAdministrator($username))) { die "Error: you are not the admin.\n"; } # communicate with file server using a file handle $fh = GetServerFileHandle("myserver"); print $fh "$cmd $argstr\n";
Bad · Perl
CVE IDTitleCVSSSeverityPublished
CVE-2025-32072 HTML injection in feed output from i18n message — Mediawiki Core - Feed Utils 6.5AIMediumAI2025-04-11
CVE-2025-32074 XSSes in Extension:ConfirmAccount — Mediawiki - Confirm Account Extension 6.1AIMediumAI2025-04-11
CVE-2025-30657 Junos OS: Processing of a specific BGP update causes the SRRD process to crash — Junos OS 5.3 Medium2025-04-09
CVE-2025-30345 OpenSlides 安全漏洞 — OpenSlides 3.5 Low2025-03-21
CVE-2024-50629 Synology DiskStation Manager（DSM）和Synology BeeStation Manager 安全漏洞 — DiskStation Manager (DSM) 5.3 Medium2025-03-19
CVE-2024-10441 Synology DiskStation Manager（DSM）和Synology BeeStation Manager 安全漏洞 — DiskStation Manager (DSM) 9.8 Critical2025-03-19
CVE-2025-27109 Lack of Escaping of HTML in JSX Fragments allows for Cross-site Scripting in solid-js — solid 7.3 High2025-02-21
CVE-2025-24025 Coolify Vulnerable to Reflected XSS on Tag Search — coolify 5.4 -2025-01-24
CVE-2024-56277 WordPress Poll Maker Plugin < 5.5.5 - HTML Injection vulnerability — Poll Maker 5.3 Medium2025-01-21
CVE-2025-23207 \htmlData does not validate attribute names in KaTeX — KaTeX 6.3 Medium2025-01-17
CVE-2024-52005 The sideband payload is passed unfiltered to the terminal in git — git 8.2 -2025-01-15
CVE-2024-50349 Git does not sanitize URLs when asking for credentials interactively — git 8.8 -2025-01-14
CVE-2024-52006 Newline confusion in credential helpers can lead to credential exfiltration in git — git 8.8 -2025-01-14
CVE-2024-9427 Koji: escape html tag characters in the query string 5.4 Medium2024-12-24
CVE-2024-55663 XWiki Platform has an SQL injection in getdocuments.vm with sort parameter — xwiki-platform 8.8 -2024-12-12
CVE-2024-47845 CSS sanitizer used incorrectly, and is easily bypassed — Mediawiki - CSS Extension 9.4 -2024-10-05
CVE-2024-47528 LibreNMS Contains a Stored XSS via File Upload — librenms 4.8 -2024-10-01
CVE-2024-47531 Scout contains insufficient output escaping of attachment names — scout 4.6 Medium2024-09-30
CVE-2024-4099 Improper Encoding or Escaping of Output in GitLab — GitLab 3.1 Low2024-09-26
CVE-2024-45498 Apache Airflow: Command Injection in an example DAG — Apache Airflow 8.8 -2024-09-07
CVE-2024-45299 alf.io's preloaded data as json is not escaped correctly — alf.io 6.5 Medium2024-09-06
CVE-2024-38177 Windows App Installer Spoofing Vulnerability — App Installer 7.8 High2024-08-13
CVE-2024-6329 Improper Encoding or Escaping of Output in GitLab — GitLab 5.7 Medium2024-08-08
CVE-2024-39682 WordPress Cooked Plugin - Authenticated (Contributor+) HTML Injection via Recipe Excerpt — Cooked 6.4 Medium2024-07-17
CVE-2024-38475 Apache HTTP Server weakness in mod_rewrite when first segment of substitution matches filesystem path. — Apache HTTP Server 9.8AICriticalAI2024-07-01
CVE-2024-38474 Apache HTTP Server weakness with encoded question marks in backreferences — Apache HTTP Server 9.8AICriticalAI2024-07-01
CVE-2024-38473 Apache HTTP Server proxy encoding problem — Apache HTTP Server 9.8AICriticalAI2024-07-01
CVE-2024-5585 Command injection via array-ish $command parameter of proc_open() (bypass CVE-2024-1874 fix) — PHP 7.7 High2024-06-09
CVE-2024-4177 Host whitelist parser issue in GravityZone Console On-Premise (VA-11554) — GravityZone Console On-Premise 8.1 High2024-06-06
CVE-2024-4420 Denial of Service in Tink-cc — Tink 7.5AIHighAI2024-05-21

Vulnerabilities classified as CWE-116 (对输出编码和转义不恰当) represent 128 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.