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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23911 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-53093 TabberNeue vulnerable to Stored XSS through wikitext — mediawiki-extensions-TabberNeue 8.6 High 2025-06-27
CVE-2025-53336 WordPress My Resume Builder plugin <= 1.0.3 - Cross Site Scripting (XSS) Vulnerability — My Resume Builder 6.5 Medium 2025-06-27
CVE-2025-53325 WordPress Beauty Contact Popup Form plugin <= 6.0 - Cross Site Scripting (XSS) Vulnerability — Beauty Contact Popup Form 5.9 Medium 2025-06-27
CVE-2025-53321 WordPress Raise The Money plugin <= 5.2 - Cross Site Scripting (XSS) Vulnerability — Raise The Money 6.5 Medium 2025-06-27
CVE-2025-53320 WordPress Free Downloads EDD plugin <= 1.0.4 - Cross Site Scripting (XSS) Vulnerability — Free Downloads EDD 6.5 Medium 2025-06-27
CVE-2025-53301 WordPress Theme Junkie Team Content plugin <= 0.1.1 - Cross Site Scripting (XSS) Vulnerability — Theme Junkie Team Content 6.5 Medium 2025-06-27
CVE-2025-53300 WordPress Podcast Feed Player Widget and Shortcode plugin <= 2.2.0 - Cross Site Scripting (XSS) Vulnerability — Podcast Feed Player Widget and Shortcode 6.5 Medium 2025-06-27
CVE-2025-53296 WordPress EC Stars Rating plugin <= 1.0.11 - Cross Site Scripting (XSS) Vulnerability — EC Stars Rating 5.9 Medium 2025-06-27
CVE-2025-53294 WordPress Smart Agenda plugin <= 4.9 - Cross Site Scripting (XSS) Vulnerability — Smart Agenda 6.5 Medium 2025-06-27
CVE-2025-53292 WordPress WP DataTable plugin <= 0.2.7 - Cross Site Scripting (XSS) Vulnerability — WP DataTable 6.5 Medium 2025-06-27
CVE-2025-53290 WordPress WP Visual Sitemap plugin <= 1.0.2 - Cross Site Scripting (XSS) Vulnerability — WP Visual Sitemap 6.5 Medium 2025-06-27
CVE-2025-53287 WordPress Quick Favicon plugin <= 0.22.8 - Cross Site Scripting (XSS) Vulnerability — Quick Favicon 5.9 Medium 2025-06-27
CVE-2025-53285 WordPress Add & Replace Affiliate Links for Amazon plugin <= 1.0.6 - Cross Site Scripting (XSS) Vulnerability — Add & Replace Affiliate Links for Amazon 5.9 Medium 2025-06-27
CVE-2025-53282 WordPress Thumbnail Editor plugin <= 2.3.3 - Cross Site Scripting (XSS) Vulnerability — Thumbnail Editor 6.5 Medium 2025-06-27
CVE-2025-53279 WordPress Popup addon for Ninja Forms plugin <= 3.4 - Cross Site Scripting (XSS) Vulnerability — Popup addon for Ninja Forms 6.5 Medium 2025-06-27
CVE-2025-53280 WordPress Football Pool plugin <= 2.12.5 - Cross Site Scripting (XSS) Vulnerability — Football Pool 6.5 Medium 2025-06-27
CVE-2025-53278 WordPress WP AdCenter plugin <= 2.6.0 - Cross Site Scripting (XSS) Vulnerability — WP AdCenter 6.5 Medium 2025-06-27
CVE-2025-53276 WordPress Omnipress plugin <= 1.6.4 - Cross Site Scripting (XSS) vulnerability — Omnipress 6.5 Medium 2025-06-27
CVE-2025-53275 WordPress Leyka plugin <= 3.32.1 - Cross Site Scripting (XSS) vulnerability — Leyka 6.5 Medium 2025-06-27
CVE-2025-53253 WordPress WP Edit plugin <= 4.0.4 - Cross Site Scripting (XSS) Vulnerability — WP Edit 5.9 Medium 2025-06-27
CVE-2025-53206 WordPress HT Mega – Absolute Addons for WPBakery Page Builder plugin <= 1.0.8 - Cross Site Scripting (XSS) Vulnerability — HT Mega – Absolute Addons for WPBakery Page Builder 6.5 Medium 2025-06-27
CVE-2025-53202 WordPress Responsive Blocks plugin <= 2.0.6 - Cross Site Scripting (XSS) Vulnerability — Responsive Blocks 6.5 Medium 2025-06-27
CVE-2025-53199 WordPress HT Slider For Elementor plugin <= 1.6.5 - Cross Site Scripting (XSS) Vulnerability — HT Slider For Elementor 6.5 Medium 2025-06-27
CVE-2025-24774 WordPress WPCRM - CRM for Contact form CF7 & WooCommerce plugin <= 3.2.0 - Reflected Cross Site Scripting (XSS) vulnerability — WPCRM - CRM for Contact form CF7 & WooCommerce 7.1 High 2025-06-27
CVE-2025-27361 WordPress Photo Express for Google plugin <= 0.3.2 - Reflected Cross Site Scripting (XSS) vulnerability — Photo Express for Google 7.1 High 2025-06-27
CVE-2025-25173 WordPress FastBook plugin <= 1.1 - Cross Site Scripting (XSS) Vulnerability — FastBook 7.1 High 2025-06-27
CVE-2025-28956 WordPress Backwp plugin <= 2.0.2 - Reflected Cross Site Scripting (XSS) vulnerability — Backwp 7.1 High 2025-06-27
CVE-2025-28960 WordPress Evangelische Termine plugin <= 3.3 - Cross Site Scripting (XSS) Vulnerability — Evangelische Termine 7.1 High 2025-06-27
CVE-2025-28988 WordPress WP Front User Submit / Front Editor plugin <= 4.9.3 - Reflected Cross Site Scripting (XSS) vulnerability — WP Front User Submit / Front Editor 7.1 High 2025-06-27
CVE-2025-30972 WordPress Woocommerce Line Notify plugin <= 1.1.7 - Cross Site Scripting (XSS) Vulnerability — Woocommerce Line Notify 7.1 High 2025-06-27

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