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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-79 (在Web页面生成时对输入的转义处理不恰当(跨站脚本)) — Vulnerability Class 23911

23911 vulnerabilities classified as CWE-79 (在Web页面生成时对输入的转义处理不恰当(跨站脚本)). AI Chinese analysis included.

CWE-79 represents a critical input validation weakness where software fails to properly sanitize user-supplied data before rendering it in web pages. Attackers typically exploit this vulnerability by injecting malicious scripts, often JavaScript, into trusted websites. When other users view the compromised page, the embedded code executes in their browsers, allowing the attacker to steal session cookies, hijack accounts, or redirect victims to phishing sites. This breach of trust undermines user privacy and application integrity. To prevent such attacks, developers must implement robust input validation and output encoding strategies. By strictly filtering incoming data and ensuring that all dynamic content is properly escaped before being processed by the browser, developers can neutralize dangerous inputs and effectively mitigate the risk of cross-site scripting vulnerabilities.

MITRE CWE Description
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. There are many variants of cross-site scripting, characterized by a variety of terms or involving different attack topologies. However, they all indicate the same fundamental weakness: improper neutralization of dangerous input between the adversary and a victim.
Common Consequences (3)
Access Control, Confidentiality Bypass Protection Mechanism, Read Application Data
The most common attack performed with cross-site scripting involves the disclosure of private information stored in user cookies, such as session information. Typically, a malicious user will craft a client-side script, which -- when parsed by a web browser -- performs some activity on behalf of the…
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands
In some circumstances it may be possible to run arbitrary code on a victim's computer when cross-site scripting is combined with other flaws, for example, "drive-by hacking."
Confidentiality, Integrity, Availability, Access Control Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Read Application Data
The consequence of an XSS attack is the same regardless of whether it is stored or reflected. The difference is in how the payload arrives at the server. XSS can cause a variety of problems for the end user that range in severity from an annoyance to complete account compromise. Some cross-site scri…
Mitigations (5)
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
Implementation, Architecture and Design Understand 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 Design, Implementation Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly throug…
Effectiveness: Limited
Architecture and Design For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Architecture and Design If 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.
Examples (2)
The following code displays a welcome message on a web page based on the HTTP GET username parameter (covers a Reflected XSS (Type 1) scenario).
$username = $_GET['username']; echo '<div class="header"> Welcome, ' . $username . '</div>';
Bad · PHP
http://trustedSite.example.com/welcome.php?username=<Script Language="Javascript">alert("You've been attacked!");</Script>
Attack
The following code displays a Reflected XSS (Type 1) scenario.
<% String eid = request.getParameter("eid"); %> ... Employee ID: <%= eid %>
Bad · JSP
<% protected System.Web.UI.WebControls.TextBox Login; protected System.Web.UI.WebControls.Label EmployeeID; ... EmployeeID.Text = Login.Text; %> <p><asp:label id="EmployeeID" runat="server" /></p>
Bad · ASP.NET
CVE ID Title CVSS Severity Published
CVE-2023-1609 Zhong Bang CRMEB Java save cross site scripting — CRMEB Java 3.5 Low 2023-03-23
CVE-2023-25456 WordPress Klaviyo Plugin <= 3.0.7 is vulnerable to Cross Site Scripting (XSS) — Klaviyo 5.9 Medium 2023-03-23
CVE-2023-26008 WordPress Top 10 Plugin <= 3.2.4 is vulnerable to Cross Site Scripting (XSS) — Top 10 – Popular posts plugin for WordPress 5.9 Medium 2023-03-23
CVE-2023-25992 WordPress CM Answers Plugin <= 3.1.9 is vulnerable to Cross Site Scripting (XSS) — CM Answers 5.9 Medium 2023-03-23
CVE-2023-23707 WordPress Embed Any Document – Embed PDF, Word, PowerPoint and Excel Files Plugin <= 2.7.1 is vulnerable to Cross Site Scripting (XSS) — Embed Any Document – Embed PDF, Word, PowerPoint and Excel Files 5.9 Medium 2023-03-23
CVE-2022-47145 WordPress Blockonomics Plugin <= 3.5.7 is vulnerable to Cross Site Scripting (XSS) — WordPress Bitcoin Payments – Blockonomics 7.1 High 2023-03-23
CVE-2022-47173 WordPress Connect Contact Form 7, WooCommerce To Google Sheets & Other Platforms – Advanced Form Integration Plugin <= 1.62.0 is vulnerable to Cross Site Scripting (XSS) — Connect Contact Form 7, WooCommerce To Google Sheets & Other Platforms – Advanced Form Integration 5.9 Medium 2023-03-23
CVE-2022-47589 WordPress CTT Expresso para WooCommerce Plugin <= 3.2.11 is vulnerable to Cross Site Scripting (XSS) — CTT Expresso para WooCommerce 5.9 Medium 2023-03-23
CVE-2023-22702 WordPress WPMobile.App — Android and iOS Mobile Application Plugin <= 11.13 is vulnerable to Cross Site Scripting (XSS) — WPMobile.App — Android and iOS Mobile Application 6.5 Medium 2023-03-23
CVE-2023-23722 WordPress WP eBay Product Feeds Plugin <= 3.3.1 is vulnerable to Cross Site Scripting (XSS) — WP eBay Product Feeds 5.9 Medium 2023-03-23
CVE-2023-23728 WordPress WP Flipclock Plugin <= 1.7.4 is vulnerable to Cross Site Scripting (XSS) — WP Flipclock 6.5 Medium 2023-03-23
CVE-2023-23864 WordPress Very Simple Google Maps Plugin <= 2.8.4 is vulnerable to Cross Site Scripting (XSS) — Very Simple Google Maps 6.5 Medium 2023-03-23
CVE-2023-23650 WordPress MainWP Code Snippets Extension Plugin <= 4.0.2 is vulnerable to Cross Site Scripting (XSS) — MainWP Code Snippets Extension 6.5 Medium 2023-03-23
CVE-2023-22712 WordPress TemplatesNext ToolKit Plugin <= 3.2.7 is vulnerable to Cross Site Scripting (XSS) — TemplatesNext ToolKit 6.5 Medium 2023-03-23
CVE-2023-22715 WordPress WP-CommentNavi Plugin <= 1.12.1 is vulnerable to Cross Site Scripting (XSS) — WP-CommentNavi 5.9 Medium 2023-03-23
CVE-2023-22716 WordPress OOPSpam Anti-Spam Plugin <= 1.1.35 is vulnerable to Cross Site Scripting (XSS) — OOPSpam Anti-Spam 5.9 Medium 2023-03-23
CVE-2022-47431 WordPress Open RDW kenteken voertuiginformatie Plugin <= 2.0.14 is vulnerable to Cross Site Scripting (XSS) — Open RDW kenteken voertuiginformatie 7.1 High 2023-03-23
CVE-2023-28422 WordPress Event Manager for WooCommerce Plugin <= 3.8.6 is vulnerable to Cross Site Scripting (XSS) — Event Manager and Tickets Selling Plugin for WooCommerce 5.9 Medium 2023-03-23
CVE-2023-22704 WordPress teachPress Plugin <= 8.1.8 is vulnerable to Cross Site Scripting (XSS) — teachPress 7.1 High 2023-03-23
CVE-2022-44742 WordPress Community Events Plugin <= 1.4.8 is vulnerable to Cross Site Scripting (XSS) — Community Events 4.8 Medium 2023-03-23
CVE-2022-45843 WordPress Smart Slider 3 Plugin <= 3.5.1.9 is vulnerable to Cross Site Scripting (XSS) — Smart Slider 3 5.4 Medium 2023-03-23
CVE-2023-1593 SourceCodester Automatic Question Paper Generator System cross site scripting — Automatic Question Paper Generator System 3.5 Low 2023-03-23
CVE-2023-1410 Stored XSS in Graphite FunctionDescription tooltip — Grafana 6.2 Medium 2023-03-23
CVE-2023-1051 XSS in As Koc Web Report System — Web Report System 6.1 Medium 2023-03-23
CVE-2023-28331 Moodle: xss risk when outputting database activity filter data 5.4 - 2023-03-23
CVE-2023-28332 Moodle: algebra filter xss when filter is misconfigured 6.1 - 2023-03-23
CVE-2023-26283 IBM WebSphere Application Server cross-site scripting — WebSphere Application Server 5.4 Medium 2023-03-22
CVE-2023-28439 ckeditor4 plugins vulnerable to cross-site scripting caused by the editor instance destroying process — ckeditor4 4.7 Medium 2023-03-22
CVE-2023-1573 DataGear Graph Dataset cross site scripting — DataGear 3.5 Low 2023-03-22
CVE-2023-1569 SourceCodester E-Commerce System cross site scripting — E-Commerce System 3.5 Low 2023-03-22

Vulnerabilities classified as CWE-79 (在Web页面生成时对输入的转义处理不恰当(跨站脚本)) represent 23911 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.