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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

23840 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-2026-55793 Craft CMS: Stored XSS via Structure entry title in table view — cms - - 2026-07-01
CVE-2026-54263 Wagtail: Reflected XSS in dynamic image URL generator view — wagtail 7.3 High 2026-07-01
CVE-2026-54720 Silverstripe Framework: Possible XSS attack through media embed — silverstripe-framework 5.4 Medium 2026-07-01
CVE-2026-55660 TinaCMS: Cross-origin postMessage handlers and rich-text URL-sanitization bypass enable stored XSS and session takeover — tinacms - - 2026-07-01
CVE-2026-55661 TinaCMS rich-text (slatejson) rendering does not sanitize link/image URLs, allowing stored XSS via dangerous URL schemes — tinacms - - 2026-07-01
CVE-2026-58263 Jodit Editor: Mutation XSS in jodit clean-html via a MathML/style rawtext carrier — jodit 7.2 High 2026-07-01
CVE-2026-14358 Stored XSS in Wikimedia Chart pie tooltip via Data:*.tab field title — Mediawiki - Charts Extension - - 2026-07-01
CVE-2026-57737 WordPress Shortcodes and extra features for Phlox theme plugin <= 2.17.16 - Cross Site Scripting (XSS) vulnerability — Shortcodes and extra features for Phlox theme 6.5 Medium 2026-07-01
CVE-2026-57722 WordPress Enable Media Replace plugin <= 4.2.1 - Cross Site Scripting (XSS) vulnerability — Enable Media Replace 5.9 Medium 2026-07-01
CVE-2026-34098 Guardian Language-System XSS via id Parameter in media.php — language-system 4.6 Medium 2026-07-01
CVE-2026-34097 Guardian Language-System XSS via id Parameter in text_file.php — language-system 4.6 Medium 2026-07-01
CVE-2026-34096 Guardian Language-System XSS via name Parameter in designer.php — language-system 4.6 Medium 2026-07-01
CVE-2026-58028 Pretty-printed API output combined with centralauthtoken allows XSS with certain gadgets — MediaWiki - - 2026-07-01
CVE-2026-58038 Stored XSS through javascript URLs in SVGs generated by EasyTimeline — timeline - - 2026-07-01
CVE-2026-58030 SyntaxHighlight stored XSS via unsanitized 'linelinks' attribute — SyntaxHighlight_GeSHi - - 2026-07-01
CVE-2026-58032 mw.Api.getErrorMessage() may return injected HTML if used without errorformat=html — MediaWiki - - 2026-07-01
CVE-2026-58037 Core log entries for exceptions and XSS issues in log entry formatting code that may be caused by user-controlled input — MediaWiki - - 2026-07-01
CVE-2026-58031 Stored i18n XSS in Special:ApiSandbox when a deprecated module is selected — MediaWiki - - 2026-07-01
CVE-2026-58034 Stored XSS through a system message when blocking a temporary account that's related to other temporary accounts — CheckUser - - 2026-07-01
CVE-2026-6283 Stored XSS in DivvyDrive Information Technologies' DivvyDrive — DivvyDrive 5.4 Medium 2026-07-01
CVE-2026-58035 Stored XSS through a system message in the codex version of Special:Block — MediaWiki - - 2026-07-01
CVE-2026-5220 Stored XSS in DivvyDrive Information Technologies' DivvyDrive — DivvyDrive 6.4 Medium 2026-07-01
CVE-2026-53907 Stored Cross‑Site Scripting in MCO — MCO - - 2026-07-01
CVE-2026-13323 Eclipse Foundation Eclipse Open VSX 跨站脚本漏洞 — Eclipse Open VSX 4.1 Medium 2026-07-01
CVE-2026-12142 NEX-Forms <= 9.2.2 - Unauthenticated Stored Cross-Site Scripting via '_name[]' Array Parameter — NEX-Forms – Ultimate Forms Plugin for WordPress 7.2 High 2026-07-01
CVE-2026-10095 WP Photo Album Plus <= 9.1.13.005 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'subtext' Shortcode Attribute — WP Photo Album Plus 6.4 Medium 2026-07-01
CVE-2026-12754 VikBooking Hotel Booking Engine & PMS <= 1.8.12 - Reflected Cross-Site Scripting via 'layoutstyle' Parameter — VikBooking Hotel Booking Engine & PMS 6.1 Medium 2026-07-01
CVE-2026-13733 Download Manager <= 3.3.60 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'no_data_msg' Shortcode Attribute — Download Manager 6.4 Medium 2026-07-01
CVE-2026-12732 LearnPress <= 4.4.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'class_wrapper_form' Shortcode Attribute — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 6.4 Medium 2026-07-01
CVE-2026-11380 JetWidgets For Elementor <= 1.0.21 - Authenticated (Author+) Stored Cross-Site Scripting via Animated Box 'animation_effect' Setting — JetWidgets For Elementor 6.4 Medium 2026-07-01

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