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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23915 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-2164 pixelstats <= 0.8.2 - Reflected Cross-Site Scripting — pixelstats 6.1 Medium 2025-03-15
CVE-2025-2163 Zoorum Comments <= 0.9 - Cross-Site Request Forgery to Stored Cross-Site Scripting — Zoorum Comments 6.1 Medium 2025-03-15
CVE-2025-29782 WeGIA Cross-Site Scripting (XSS) Stored in endpoint `adicionar_tipo_docs_atendido.php` parameter `tipo` — WeGIA 5.4 - 2025-03-14
CVE-2025-29771 HtmlSanitizer vulnerable to XSS when used with contentEditable — HtmlSanitizer 6.1 - 2025-03-14
CVE-2024-12020 Reflected Cross-Site Scripting (XSS) — LogicalDOC Enterprise 6.1 - 2025-03-14
CVE-2025-1888 Reflected Cross Site Scripting in Aperio Eslide Manager — Aperio Eslide Manager 4.6 Medium 2025-03-14
CVE-2025-26626 GLPI Inventory Plugin vulnerable to reflective Cross-site Scripting — glpi-inventory-plugin 6.5 Medium 2025-03-14
CVE-2024-26006 Fortinet FortiOS 安全漏洞 — FortiProxy 6.9 High 2025-03-14
CVE-2025-1526 DethemeKit for Elementor <= 2.1.9 - Authenticated (Contributor+) Stored Cross-Site Scripting — DethemeKit for Elementor 6.4 Medium 2025-03-14
CVE-2025-2166 CM FAQ – Simplify support with an intuitive FAQ management tool <= 1.2.5 - Reflected Cross-Site Scripting — CM FAQ – Simplify support with an intuitive FAQ management tool 6.1 Medium 2025-03-14
CVE-2025-1503 WP Recipe Maker <= 9.8.0 - Authenticated (Contributor+) Stored Cross-Site Scripting — WP Recipe Maker 6.4 Medium 2025-03-13
CVE-2025-1561 AppPresser – Mobile App Framework <= 4.4.10 - Unauthenticated Stored Cross-Site Scripting — AppPresser – Mobile App Framework 7.2 High 2025-03-13
CVE-2025-1559 CC-IMG-Shortcode <= 1.1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting — CC-IMG-Shortcode 6.4 Medium 2025-03-13
CVE-2025-27867 Apache Felix HTTP Webconsole Plugin: XSS in HTTP Webconsole Plugin — Apache Felix HTTP Webconsole Plugin 6.1 - 2025-03-12
CVE-2025-1527 ShopLentor – WooCommerce Builder for Elementor & Gutenberg +20 Modules – All in One Solution (formerly WooLentor) <= 3.1.0 - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via Flash Sale Countdown Module — ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin 6.4 Medium 2025-03-12
CVE-2024-12589 Finale Lite – Sales Countdown Timer & Discount for WooCommerce <= 2.19.0 - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via Countdown Timer — Finale Lite – Sales Countdown Timer & Discount for WooCommerce 6.4 Medium 2025-03-12
CVE-2025-2077 Simple Amazon Affiliate <= 1.0.9 - Reflected Cross-Site Scripting — Simple Amazon Affiliate 6.1 Medium 2025-03-12
CVE-2025-2078 BlogBuzzTime-for-wp <= 1.1 - Authenticated (Admin+) Stored Cross-Site Scripting — BlogBuzzTime for WP 4.4 Medium 2025-03-12
CVE-2025-2205 GDPR Cookie Compliance <= 4.15.6 - Authenticated (Admin+) Stored Cross-Site Scripting — GDPR Cookie Compliance – Cookie Banner, Cookie Consent, Cookie Notice for CCPA, EU Cookie Law 4.4 Medium 2025-03-12
CVE-2025-2076 binlayerpress <= 1.1 - Authenticated (Admin+) Stored Cross-Site Scripting — binlayerpress 4.4 Medium 2025-03-12
CVE-2025-2214 Microweber Settings index.php cross site scripting — Microweber 3.5 Low 2025-03-11
CVE-2025-2213 Castlenet CBW383G2N Wireless Menu wlanPrimaryNetwork.asp cross site scripting — CBW383G2N 2.4 Low 2025-03-11
CVE-2025-2212 Castlenet CBW383G2N RgSwInfo.asp cross site scripting — CBW383G2N 2.4 Low 2025-03-11
CVE-2025-2211 aitangbao springboot-manager add cross site scripting — springboot-manager 2.4 Low 2025-03-11
CVE-2025-2210 aitangbao springboot-manager add cross site scripting — springboot-manager 2.4 Low 2025-03-11
CVE-2025-2209 aitangbao springboot-manager add cross site scripting — springboot-manager 2.4 Low 2025-03-11
CVE-2025-28943 WordPress DP ALTerminator - Missing ALT manager Plugin <= 1.0.2 - Cross Site Scripting (XSS) vulnerability — DP ALTerminator - Missing ALT manager 5.9 Medium 2025-03-11
CVE-2025-28937 WordPress Lava Ajax Search plugin <= 1.1.9 - Cross Site Scripting (XSS) vulnerability — Lava Ajax Search 5.9 Medium 2025-03-11
CVE-2025-28936 WordPress Lunar plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability — Lunar 5.9 Medium 2025-03-11
CVE-2025-28930 WordPress List Mixcloud plugin <= 1.4 - Cross Site Scripting (XSS) vulnerability — List Mixcloud 6.5 Medium 2025-03-11

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