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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23919 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-27621 WordPress Livestream Notice Plugin <= 1.2.0 is vulnerable to Cross Site Scripting (XSS) — Livestream Notice 5.9 Medium 2023-08-30
CVE-2023-24401 WordPress Mobile Call Now & Map Buttons Plugin <= 1.5.0 is vulnerable to Cross Site Scripting (XSS) — Mobile Call Now & Map Buttons 5.9 Medium 2023-08-30
CVE-2023-24397 WordPress Reservation.Studio widget Plugin <= 1.0.11 is vulnerable to Cross Site Scripting (XSS) — Reservation.Studio widget 5.9 Medium 2023-08-30
CVE-2023-25471 WordPress WCP OpenWeather Plugin <= 2.5.0 is vulnerable to Cross Site Scripting (XSS) — WCP OpenWeather 7.1 High 2023-08-30
CVE-2023-28415 WordPress Side Cart Woocommerce (Ajax) Plugin <= 2.2 is vulnerable to Cross Site Scripting (XSS) — Side Cart Woocommerce (Ajax) 5.9 Medium 2023-08-30
CVE-2023-28692 WordPress WP Abstracts Plugin <= 2.6.3 is vulnerable to Cross Site Scripting (XSS) — WP Abstracts 5.9 Medium 2023-08-30
CVE-2023-25466 WordPress Who Hit The Page – Hit Counter Plugin <= 1.4.14.3 is vulnerable to Cross Site Scripting (XSS) — Who Hit The Page – Hit Counter 5.8 Medium 2023-08-30
CVE-2023-35092 WordPress breadcrumb simple Plugin <= 1.3 is vulnerable to Cross Site Scripting (XSS) — Breadcrumb simple 5.9 Medium 2023-08-30
CVE-2023-35094 WordPress WP Matterport Shortcode Plugin <= 2.1.4 is vulnerable to Cross Site Scripting (XSS) — WP Matterport Shortcode 6.5 Medium 2023-08-30
CVE-2023-25453 WordPress WordPress Tables Plugin <= 1.3.9 is vulnerable to Cross Site Scripting (XSS) — WordPress Tables 7.1 High 2023-08-30
CVE-2023-34372 WordPress Download SpamReferrerBlock Plugin <= 2.22 is vulnerable to Cross Site Scripting (XSS) — SpamReferrerBlock 5.9 Medium 2023-08-30
CVE-2023-32294 WordPress GDPR Cookie Consent Notice Box Plugin <= 1.1.6 is vulnerable to Cross Site Scripting (XSS) — GDPR Cookie Consent Notice Box 5.9 Medium 2023-08-30
CVE-2023-34004 WordPress WooCommerce Box Office Plugin <= 1.1.50 is vulnerable to Cross Site Scripting (XSS) — WooCommerce Box Office 6.5 Medium 2023-08-30
CVE-2023-34008 WordPress WP ERP Plugin <= 1.12.3 is vulnerable to Cross Site Scripting (XSS) — WP ERP 7.1 High 2023-08-30
CVE-2023-34022 WordPress Dynamic QR Code Generator Plugin <= 0.0.5 is vulnerable to Cross Site Scripting (XSS) — Dynamic QR Code Generator 7.1 High 2023-08-30
CVE-2023-34023 WordPress WordPress Social Login Plugin <= 3.0.4 is vulnerable to Cross Site Scripting (XSS) — WordPress Social Login 7.1 High 2023-08-30
CVE-2023-34032 WordPress bbPress Toolkit Plugin <= 1.0.12 is vulnerable to Cross Site Scripting (XSS) — bbPress Toolkit 7.1 High 2023-08-30
CVE-2023-34172 WordPress WordPress Social Login Plugin <= 3.0.4 is vulnerable to Cross Site Scripting (XSS) — WordPress Social Login 5.9 Medium 2023-08-30
CVE-2023-34173 WordPress Yandex Metrica Counter Plugin <= 1.4.3 is vulnerable to Cross Site Scripting (XSS) — Yandex Metrica Counter 5.9 Medium 2023-08-30
CVE-2023-34174 WordPress BBS e-Popup Plugin <= 2.4.5 is vulnerable to Cross Site Scripting (XSS) — BBS e-Popup 7.1 High 2023-08-30
CVE-2023-34180 WordPress Google Fonts For WordPress Plugin <= 3.0.0 is vulnerable to Cross Site Scripting (XSS) — Google Fonts For WordPress 7.1 High 2023-08-30
CVE-2023-34175 WordPress Login Configurator Plugin <= 2.1 is vulnerable to Cross Site Scripting (XSS) — Login Configurator 7.1 High 2023-08-30
CVE-2023-34176 WordPress Chilexpress woo oficial Plugin <= 1.2.9 is vulnerable to Cross Site Scripting (XSS) — Chilexpress woo oficial 7.1 High 2023-08-30
CVE-2023-34184 WordPress Woocommerce Order address Print Plugin <= 3.2 is vulnerable to Cross Site Scripting (XSS) — Woocommerce Order address Print 7.1 High 2023-08-30
CVE-2023-34183 WordPress Unite Gallery Lite Plugin <= 1.7.61 is vulnerable to Cross Site Scripting (XSS) — Unite Gallery Lite 5.9 Medium 2023-08-30
CVE-2023-34187 WordPress Call Now Icon Animate Plugin <= 0.1.0 is vulnerable to Cross Site Scripting (XSS) — Call Now Icon Animate 5.9 Medium 2023-08-30
CVE-2023-27426 WordPress NotifyVisitors Plugin <= 1.0 is vulnerable to Cross Site Scripting (XSS) — NotifyVisitors 5.9 Medium 2023-08-30
CVE-2023-33929 WordPress Easy Admin Menu Plugin <= 1.3 is vulnerable to Cross Site Scripting (XSS) — Easy Admin Menu 5.9 Medium 2023-08-30
CVE-2023-33320 WordPress WP-Hijri Plugin <= 1.5.1 is vulnerable to Cross Site Scripting (XSS) — WP-Hijri 7.1 High 2023-08-30
CVE-2023-33325 WordPress Leyka Plugin <= 3.30.1 is vulnerable to Cross Site Scripting (XSS) — Leyka 7.1 High 2023-08-30

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