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-68460 Roundcube Webmail 安全漏洞 — Webmail 7.2 High2025-12-18
CVE-2025-12734 Improper Encoding or Escaping of Output in GitLab — GitLab 3.5 Low2025-12-11
CVE-2025-8405 Improper Encoding or Escaping of Output in GitLab — GitLab 7.7 High2025-12-11
CVE-2025-42896 Server-Side Request Forgery (SSRF) in SAP BusinessObjects Business Intelligence Platform — SAP BusinessObjects Business Intelligence Platform 5.4 Medium2025-12-09
CVE-2025-66548 Nextcloud Deck app allows to spoof file extensions by using RTLO characters — security-advisories 3.3 Low2025-12-05
CVE-2025-9127 PX Enterprise Improper Sanitization Vulnerability — PX Enterprise 6.5AIMediumAI2025-12-04
CVE-2025-40547 SolarWinds Serv-U Logic Abuse - Remote Code Execution Vulnerability — Serv-U 9.1 Critical2025-11-18
CVE-2025-11085 FactoryTalk® DataMosaix™ Private Cloud – Persistent XSS — FactoryTalk® DataMosaix™ Private Cloud 6.1 -2025-11-11
CVE-2025-46583 DOS Vulnerability in ZTE MC889A Pro product — MC889A Pro 5.3 Medium2025-10-27
CVE-2025-61912 python-ldap Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination — python-ldap 7.5AIHighAI2025-10-10
CVE-2025-0607 HTML Injection in Logo Software's Logo Cloud — Logo Cloud 4.3 Medium2025-10-06
CVE-2025-59936 get-jwks poisoned JWKS cache allows post-fetch issuer validation bypass — get-jwks 5.9 -2025-09-27
CVE-2025-57880 Potential XSS in Extension:BlueSpiceWhoIsOnline — BlueSpice 6.1 -2025-09-19
CVE-2025-48007 Potential XSS in Extension:BlueSpiceAvatars — BlueSpice 6.1 -2025-09-19
CVE-2025-46703 Potential XSS in Extension:AtMentions — BlueSpice 6.1 -2025-09-19
CVE-2025-55730 XWiki Remote Macros vulnerable to remote code execution using the confluence paste code macro — xwiki-pro-macros 10.0 Critical2025-09-09
CVE-2025-55729 XWiki Remote Macros vulnerable to remote code execution using the ConfluenceLayoutSection macro — xwiki-pro-macros 10.0 Critical2025-09-09
CVE-2024-58266 shlex crate 安全漏洞 — shlex 3.2 Low2025-07-27
CVE-2025-48062 Discourse vulnerable to HTML injection when inviting to topic via email — discourse 7.1 High2025-06-09
CVE-2025-25029 IBM Security Guardium information disclosure — Security Guardium 4.9 Medium2025-05-28
CVE-2021-25262 Yandex Browser for Android prior to version 21.3.0 allows remote attackers to perform IDN homograph attack. — Browser 4.3AIMediumAI2025-05-21
CVE-2021-25254 Yandex Browser Lite for Android before 21.1.0 allows remote attackers to spoof the address bar. — Browser Lite 5.3AIMediumAI2025-05-21
CVE-2025-1308 PX Backup Improper Sanitization Vulnerability — PX Backup 6.5AIMediumAI2025-05-19
CVE-2025-47280 Umbraco.Forms has HTML injection vulnerability in 'Send email' workflow — Umbraco.Forms.Issues 4.7AIMediumAI2025-05-13
CVE-2025-32974 org.xwiki.platform:xwiki-platform-security-requiredrights-default required rights analysis doesn't consider TextAreas with default content type — xwiki-platform 9.1 Critical2025-04-30
CVE-2025-24338 Bosch Rexroth ctrlX OS 安全漏洞 — ctrlX OS - Solutions 7.1 High2025-04-30
CVE-2025-46347 YesWiki Remote Code Execution via Arbitrary PHP File Write and Execution — yeswiki 8.8AIHighAI2025-04-29
CVE-2025-31651 Apache Tomcat: Bypass of rules in Rewrite Valve — Apache Tomcat 9.1AICriticalAI2025-04-28
CVE-2025-23377 Dell PowerProtect Data Manager Reporting 安全漏洞 — PowerProtect Data Manager 4.2 Medium2025-04-28
CVE-2025-32078 XSSes and potential RCE in Special:VersionCompare — Mediawiki - Version Compare Extension 6.1AIMediumAI2025-04-11

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