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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23918 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-25169 WordPress Authors Autocomplete Meta Box plugin <= 1.2 - Reflected Cross Site Scripting (XSS) vulnerability — Authors Autocomplete Meta Box 7.1 High 2025-03-03
CVE-2025-25164 WordPress Meta Accelerator plugin <= 1.0.4 - Reflected Cross Site Scripting (XSS) vulnerability — Meta Accelerator 7.1 High 2025-03-03
CVE-2025-25165 WordPress Staff Directory Plugin: Company Directory Plugin <= 4.3 - Cross Site Scripting (XSS) vulnerability — Staff Directory Plugin: Company Directory 7.1 High 2025-03-03
CVE-2025-25133 WordPress WP Frontend Submit Plugin <= 1.1.0 - Reflected Cross-Site Scripting vulnerability — WP Frontend Submit 7.1 High 2025-03-03
CVE-2025-25157 WordPress WP Church Center Plugin <= 1.3.3 - Reflected Cross Site Scripting (XSS) vulnerability — WP Church Center 7.1 High 2025-03-03
CVE-2025-25132 WordPress Visitor Details plugin <= 1.0.1 - Cross Site Scripting (XSS) vulnerability — Visitor Details 7.1 High 2025-03-03
CVE-2025-25142 WordPress WP Less Compiler plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability — WP Less Compiler 7.1 High 2025-03-03
CVE-2025-25124 WordPress Status Updater Plugin <= 9.21 - Reflected Cross Site Scripting (XSS) vulnerability — Status Updater 7.1 High 2025-03-03
CVE-2025-25129 WordPress Callback Request plugin <= 1.4 - Reflected Cross Site Scripting (XSS) vulnerability — Callback Request 7.1 High 2025-03-03
CVE-2025-25131 WordPress RJ Quickcharts plugin <= 0.6.1 - Cross Site Scripting (XSS) vulnerability — RJ Quickcharts 6.5 Medium 2025-03-03
CVE-2025-25127 WordPress Contact Us By Lord Linus Plugin <= 2.6 - Reflected Cross Site Scripting (XSS) vulnerability — Contact Us By Lord Linus 7.1 High 2025-03-03
CVE-2025-25118 WordPress WPOptin plugin <= 2.0.8 - Cross Site Scripting (XSS) vulnerability — Top Bar – PopUps – by WPOptin 7.1 High 2025-03-03
CVE-2025-25113 WordPress Implied Cookie Consent plugin <= 1.3 - Reflected Cross Site Scripting (XSS) vulnerability — Implied Cookie Consent 7.1 High 2025-03-03
CVE-2025-25114 WordPress User Role plugin <= 1.0 - Reflected Cross Site Scripting (XSS) vulnerability — User Role 7.1 High 2025-03-03
CVE-2025-25119 WordPress Woocommerce osCommerce Sync plugin <= 2.0.20 - Cross Site Scripting (XSS) vulnerability — Woocommerce osCommerce Sync 7.1 High 2025-03-03
CVE-2025-25115 WordPress Like dislike plus counter plugin <= 1.0 - Cross Site Scripting (XSS) vulnerability — Like dislike plus counter 6.5 Medium 2025-03-03
CVE-2025-25092 WordPress All push notification for WP plugin <= 1.5.3 - Cross Site Scripting (XSS) vulnerability — All push notification for WP 7.1 High 2025-03-03
CVE-2025-25102 WordPress Yahoo BOSS Plugin <= 0.7 - Reflected Cross Site Scripting (XSS) vulnerability — Yahoo BOSS 7.1 High 2025-03-03
CVE-2025-25099 WordPress Appointment Buddy Widget By Accrete plugin <= 1.2. - Reflected Cross-Site Scripting vulnerability — Appointment Buddy Widget 7.1 High 2025-03-03
CVE-2025-25108 WordPress SW Plus Plugin <= 2.1 - Reflected Cross Site Scripting (XSS) vulnerability — SW Plus 7.1 High 2025-03-03
CVE-2025-25090 WordPress Dreamstime Stock Photos plugin <= 4.1 - Reflected Cross Site Scripting (XSS) vulnerability — Dreamstime Stock Photos 7.1 High 2025-03-03
CVE-2025-25089 WordPress Image Rotator plugin <= 2.0 - Reflected Cross Site Scripting (XSS) vulnerability — Image Rotator 7.1 High 2025-03-03
CVE-2025-25083 WordPress EP4 More Embeds Plugin <= 1.0.0 - Stored Cross Site Scripting (XSS) vulnerability — EP4 More Embeds 7.1 High 2025-03-03
CVE-2025-25084 WordPress UniTimetable plugin <= 1.1 - Cross Site Scripting (XSS) vulnerability — UniTimetable 6.5 Medium 2025-03-03
CVE-2025-25087 WordPress seekXL Snapr plugin <= 2.0.6 - Reflected Cross Site Scripting (XSS) vulnerability — seekXL Snapr 7.1 High 2025-03-03
CVE-2025-25070 WordPress Album Reviewer plugin <= 2.0.2 - Cross Site Scripting (XSS) vulnerability — Album Reviewer 7.1 High 2025-03-03
CVE-2025-24694 WordPress CM Pop-Up Banners plugin <= 1.7.6 - Reflected Cross Site Scripting (XSS) vulnerability — CM Pop-Up banners 7.1 High 2025-03-03
CVE-2025-24758 WordPress CM Map Locations plugin <= 2.0.8 - Reflected Cross Site Scripting (XSS) vulnerability — CM Map Locations 7.1 High 2025-03-03
CVE-2025-23903 WordPress Local Shipping Labels for WooCommerce Plugin <= 1.0.0 - Reflected Cross Site Scripting (XSS) vulnerability — Local Shipping Labels for WooCommerce 7.1 High 2025-03-03
CVE-2025-23956 WordPress WP Easy Post Mailer Plugin <= 0.64 - Reflected Cross Site Scripting (XSS) vulnerability — WP Easy Post Mailer 7.1 High 2025-03-03

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