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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23912 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-2025-47617 WordPress WP Front User Submit / Front Editor plugin <= 5.0.6 - Cross Site Scripting (XSS) vulnerability — WP Front User Submit / Front Editor 5.9 Medium 2025-05-07
CVE-2025-47616 WordPress aBlocks plugin <= 1.9.2 - Cross Site Scripting (XSS) Vulnerability — aBlocks 6.5 Medium 2025-05-07
CVE-2025-47615 WordPress Amazon Product in a Post plugin <= 5.2.2 - Cross Site Scripting (XSS) Vulnerability — Amazon Product in a Post 5.9 Medium 2025-05-07
CVE-2025-47607 WordPress Show All Comments plugin <= 7.0.1 - Cross Site Scripting (XSS) Vulnerability — Show All Comments 5.9 Medium 2025-05-07
CVE-2025-47604 WordPress Inline Related Posts plugin <= 3.8.0 - Cross Site Scripting (XSS) Vulnerability — Inline Related Posts 6.5 Medium 2025-05-07
CVE-2025-47605 WordPress WP jQuery DataTable plugin <= 4.1.0 - Cross Site Scripting (XSS) Vulnerability — WP jQuery DataTable 5.9 Medium 2025-05-07
CVE-2025-47595 WordPress Color Your Bar plugin <= 2.0 - Cross Site Scripting (XSS) Vulnerability — Color Your Bar 5.9 Medium 2025-05-07
CVE-2025-47592 WordPress Legal Terms and Conditions Popup for User Login and WooCommerce Checkout – TPUL plugin <= 2.0.8 - Cross Site Scripting (XSS) Vulnerability — Terms Popup On User Login 5.9 Medium 2025-05-07
CVE-2025-47593 WordPress Really Simple Under Construction Page plugin <= 1.4.6 - Cross Site Scripting (XSS) Vulnerability — Really Simple Under Construction Page 5.9 Medium 2025-05-07
CVE-2025-47589 WordPress Ebook Store plugin <= 5.8009 - Cross Site Scripting (XSS) Vulnerability — Ebook Store 6.5 Medium 2025-05-07
CVE-2025-47547 WordPress SendPulse Email Marketing Newsletter plugin <= 2.1.6 - Cross Site Scripting (XSS) Vulnerability — SendPulse Email Marketing Newsletter 6.5 Medium 2025-05-07
CVE-2025-47525 WordPress Bold Page Builder plugin <= 5.3.0 - Cross Site Scripting (XSS) Vulnerability — Bold Page Builder 5.9 Medium 2025-05-07
CVE-2025-47524 WordPress Quran multilanguage Text & Audio plugin <= 2.3.23 - Cross Site Scripting (XSS) Vulnerability — Quran multilanguage Text & Audio 5.9 Medium 2025-05-07
CVE-2025-47522 WordPress AWEOS WP Lock plugin <= 1.4.8 - Cross Site Scripting (XSS) Vulnerability — AWEOS WP Lock 5.9 Medium 2025-05-07
CVE-2025-47521 WordPress Robo Gallery plugin <= 5.0.2 - Cross Site Scripting (XSS) Vulnerability — Robo Gallery 5.9 Medium 2025-05-07
CVE-2025-47520 WordPress Charitable plugin <= 1.8.5.1 - Cross Site Scripting (XSS) Vulnerability — Charitable 5.9 Medium 2025-05-07
CVE-2025-47518 WordPress Contact Form 7 – PayPal & Stripe Add-on plugin <= 2.3.4 - Cross Site Scripting (XSS) Vulnerability — Contact Form 7 – PayPal & Stripe Add-on 5.9 Medium 2025-05-07
CVE-2025-47516 WordPress Time Clock plugin <= 1.2.3 - Cross Site Scripting (XSS) Vulnerability — Time Clock 5.9 Medium 2025-05-07
CVE-2025-47515 WordPress WP DPE-GES plugin <= 1.6 - Cross Site Scripting (XSS) Vulnerability — WP DPE-GES 6.5 Medium 2025-05-07
CVE-2025-47509 WordPress Top 10 plugin <= 4.1.0 - Cross Site Scripting (XSS) Vulnerability — Top 10 6.5 Medium 2025-05-07
CVE-2025-47507 WordPress Better Search plugin <= 4.1.0 - Cross Site Scripting (XSS) Vulnerability — Better Search 6.5 Medium 2025-05-07
CVE-2025-47506 WordPress Contextual Related Posts plugin <= 4.0.2 - Cross Site Scripting (XSS) Vulnerability — Contextual Related Posts 6.5 Medium 2025-05-07
CVE-2025-47505 WordPress Product Time Countdown for WooCommerce plugin <= 1.6.2 - Cross Site Scripting (XSS) Vulnerability — Product Time Countdown for WooCommerce 6.5 Medium 2025-05-07
CVE-2025-47503 WordPress NGG Smart Image Search plugin <= 3.3.3 - Cross Site Scripting (XSS) Vulnerability — NGG Smart Image Search 6.5 Medium 2025-05-07
CVE-2025-47504 WordPress Custom Checkout Fields for WooCommerce plugin <= 1.8.3 - Cross Site Scripting (XSS) Vulnerability — Custom Checkout Fields for WooCommerce 6.5 Medium 2025-05-07
CVE-2025-47501 WordPress Content Control plugin <= 2.6.1 - Cross Site Scripting (XSS) Vulnerability — Content Control 6.5 Medium 2025-05-07
CVE-2025-47502 WordPress Mollie Forms plugin <= 2.7.12 - Cross Site Scripting (XSS) Vulnerability — Mollie Forms 6.5 Medium 2025-05-07
CVE-2025-47499 WordPress Simple Blog Stats plugin <= 20250416 - Cross Site Scripting (XSS) Vulnerability — Simple Blog Stats 6.5 Medium 2025-05-07
CVE-2025-47497 WordPress Logo Showcase plugin <= 3.0.4 - Cross Site Scripting (XSS) Vulnerability — Logo Showcase 6.5 Medium 2025-05-07
CVE-2025-47495 WordPress Blockspare plugin <= 3.2.9 - Cross Site Scripting (XSS) Vulnerability — Blockspare 6.5 Medium 2025-05-07

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