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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

21803 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, ConfidentialityBypass 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, AvailabilityExecute 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 ControlExecute 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 DesignUse 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 DesignUnderstand 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, ImplementationUnderstand 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 DesignFor 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 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.
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 IDTitleCVSSSeverityPublished
CVE-2024-51695 WordPress Fabrica Synced Pattern Instances plugin <= 1.0.8 - Reflected Cross Site Scripting (XSS) vulnerability — Fabrica Synced Pattern Instances 7.1 High2024-11-09
CVE-2024-51696 WordPress Content Syndication Toolkit Reader plugin <= 1.5 - Reflected Cross Site Scripting (XSS) vulnerability — Content Syndication Toolkit Reader 7.1 High2024-11-09
CVE-2024-51697 WordPress Doofinder plugin <= 0.5.4 - Reflected Cross Site Scripting (XSS) vulnerability — Doofinder 7.1 High2024-11-09
CVE-2024-51698 WordPress Master Bar plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability — Master Bar 7.1 High2024-11-09
CVE-2024-51699 WordPress Buooy Sticky Header plugin <= 0.5.2 - Reflected Cross Site Scripting (XSS) vulnerability — Buooy Sticky Header 7.1 High2024-11-09
CVE-2024-51701 WordPress MG Post Contributors plugin <= 1.3. - Reflected Cross Site Scripting (XSS) vulnerability — MG Post Contributors 7.1 High2024-11-09
CVE-2024-51702 WordPress SrcSet Responsive Images for WordPress plugin <= 1.4 - Reflected Cross Site Scripting (XSS) vulnerability — SrcSet Responsive Images for WordPress 7.1 High2024-11-09
CVE-2024-10837 SysBasics Customize My Account for WooCommerce <= 2.7.29 - Reflected Cross-Site Scripting via tab Parameter — SysBasics Customize My Account for WooCommerce 6.1 Medium2024-11-09
CVE-2024-51703 WordPress WP-Basics plugin <= 2.0 - Reflected Cross Site Scripting (XSS) vulnerability — WP-Basics 7.1 High2024-11-09
CVE-2024-51704 WordPress imPress plugin <= 0.1.4 - Reflected Cross Site Scripting (XSS) vulnerability — imPress 7.1 High2024-11-09
CVE-2024-51705 WordPress WP MMenu Lite plugin <= 1.0.0 - Reflected Cross Site Scripting (XSS) vulnerability — WP MMenu Lite 7.1 High2024-11-09
CVE-2024-51706 WordPress UW Freelancer plugin <= 0.1 - Reflected Cross Site Scripting (XSS) vulnerability — UW Freelancer 7.1 High2024-11-09
CVE-2024-51707 WordPress WP Visual Adverts plugin <= 2.3.0 - Reflected Cross Site Scripting (XSS) vulnerability — WP Visual Adverts 7.1 High2024-11-09
CVE-2024-51708 WordPress Narnoo Commerce Manager plugin <= 1.6.0 - Reflected Cross Site Scripting (XSS) vulnerability — Narnoo Commerce Manager 7.1 High2024-11-09
CVE-2024-51709 WordPress TeleAdmin plugin <= 1.0.0 - Reflected Cross Site Scripting (XSS) vulnerability — TeleAdmin 7.1 High2024-11-09
CVE-2024-51710 WordPress Responsive Data Table plugin <= 1.3 - Reflected Cross Site Scripting (XSS) vulnerability — Responsive Data Table 7.1 High2024-11-09
CVE-2024-51711 WordPress Saragna plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability — Saragna 7.1 High2024-11-09
CVE-2024-51712 WordPress Jigoshop plugin <= 1.4.0 - Reflected Cross Site Scripting (XSS) vulnerability — Jigoshop – Store Toolkit 7.1 High2024-11-09
CVE-2024-51713 WordPress HQ60 Fidelity Card plugin <= 1.8 - Reflected Cross Site Scripting (XSS) vulnerability — HQ60 Fidelity Card 7.1 High2024-11-09
CVE-2024-51714 WordPress User Password Reset plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability — User Password Reset 7.1 High2024-11-09
CVE-2024-51716 WordPress Twitter real time search scrolling plugin <= 7.0 - Reflected Cross Site Scripting (XSS) vulnerability — Twitter real time search scrolling 7.1 High2024-11-09
CVE-2024-51717 WordPress Ajax Content Filter plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability — Ajax Content Filter 7.1 High2024-11-09
CVE-2024-51718 WordPress Simple Modal plugin <= 0.3.3 - Reflected Cross Site Scripting (XSS) vulnerability — Simple Modal 7.1 High2024-11-09
CVE-2024-51719 WordPress Simplistic SEO plugin <= 2.3.0 - Reflected Cross Site Scripting (XSS) vulnerability — Simplistic SEO 7.1 High2024-11-09
CVE-2024-51759 WordPress SVT Simple plugin <= 1.0.1 - Reflected Cross Site Scripting (XSS) vulnerability — SVT Simple 7.1 High2024-11-09
CVE-2024-51760 WordPress Dashing Memberships plugin <= 1.1 - Reflected Cross Site Scripting (XSS) vulnerability — Dashing Memberships 7.1 High2024-11-09
CVE-2024-51761 WordPress WPHelpful plugin <= 1.2.4 - Reflected Cross Site Scripting (XSS) vulnerability — WPHelpful 7.1 High2024-11-09
CVE-2024-51762 WordPress PropertyShift plugin <= 1.0.0 - Reflected Cross Site Scripting (XSS) vulnerability — PropertyShift 7.1 High2024-11-09
CVE-2024-51763 WordPress Team Showcase and Slider plugin <= 1.3 - Reflected Cross Site Scripting (XSS) vulnerability — Team Showcase and Slider – Team Members Builder 7.1 High2024-11-09
CVE-2024-10676 WordPress Conversion Helper plugin <= 1.12 - Reflected Cross Site Scripting (XSS) vulnerability — Conversion Helper 7.1 High2024-11-09

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