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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-352 (跨站请求伪造(CSRF)) — Vulnerability Class 4776

4776 vulnerabilities classified as CWE-352 (跨站请求伪造(CSRF)). AI Chinese analysis included.

CWE-352, Cross-Site Request Forgery, is a web application weakness where the system fails to verify that an incoming request was intentionally initiated by the authenticated user rather than an unauthorized actor. Attackers typically exploit this vulnerability by tricking a victim into submitting a malicious request, often via a hidden link or form on a third-party site, while the victim is logged into the target application. Because the browser automatically includes valid session cookies, the server processes the forged request as legitimate, potentially allowing unauthorized actions like fund transfers or profile changes. Developers mitigate this risk by implementing anti-CSRF tokens, synchronizer tokens, or validating the Origin and Referer headers to ensure requests originate from trusted sources, thereby preventing unauthorized state changes.

MITRE CWE Description
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Common Consequences (1)
Confidentiality, Integrity, Availability, Non-Repudiation, Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism, Read Application Data, Modify Application Data, DoS: Crash, Exit, or Restart
The consequences will vary depending on the nature of the functionality that is vulnerable to CSRF. An attacker could trick a client into making an unintentional request to the web server via a URL, image load, XMLHttpRequest, etc., which would then be treated as an authentic request from the client…
Mitigations (5)
Architecture and DesignUse 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]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
ImplementationEnsure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
Architecture and DesignIdentify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Architecture and DesignUse the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the f…
Examples (1)
This example PHP code attempts to secure the form submission process by validating that the user submitting the form has a valid session. A CSRF attack would not be prevented by this countermeasure because the attacker forges a request through the user's web browser in which a valid session already exists.
<form action="/url/profile.php" method="post"> <input type="text" name="firstname"/> <input type="text" name="lastname"/> <br/> <input type="text" name="email"/> <input type="submit" name="submit" value="Update"/> </form>
Bad · HTML
// initiate the session in order to validate sessions session_start(); //if the session is registered to a valid user then allow update if (! session_is_registered("username")) { echo "invalid session detected!"; // Redirect user to login page [...] exit; } // The user session is valid, so process the request // and update the information update_profile(); function update_profile { // read in the data from $POST and send an update // to the database SendUpdateToDatabase($_SESSION['username'], $_POST['email']); [...] echo "Your profile has been successfully updated."; }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2022-29454 WordPress Better Messages plugin <= 1.9.9.148 - Cross-Site Request Forgery (CSRF) vulnerability — Better Messages (WordPress plugin) 3.1 Low2022-07-20
CVE-2022-2224 Gallery for Social Photo <= 1.0.0.27 - Cross-Site Request Forgery to Post Duplication — Gallery for Social Photo 5.4 Medium2022-07-18
CVE-2022-2443 FreeMind WP Browser <= 1.2 - Cross-Site Request Forgery to Cross-Site Scripting — FreeMind WP Browser 8.8 High2022-07-18
CVE-2022-2001 DX Share Selection <= 1.4 - Cross-Site Request Forgery to Cross-Site Scripting — DX Share Selection 8.8 High2022-07-18
CVE-2022-1912 Button Widget Smartsoft <= 1.0.1 - Cross-Site Request Forgery to Cross-Site Scripting — Button Widget Smartsoft 8.8 High2022-07-18
CVE-2022-2435 AnyMind Widget <= 1.1 - Cross-Site Request Forgery to Cross-Site Scripting — AnyMind Widget 8.8 High2022-07-18
CVE-2022-2223 Image Slider <= 1.1.121 - Cross-Site Request Forgery to Post Duplication — Image Slider 5.4 Medium2022-07-18
CVE-2022-2039 Free Live Chat Support <= 1.0.11 - Cross-Site Request Forgery to Cross-Site Scripting — Free Live Chat Support 8.8 High2022-07-18
CVE-2022-2144 Jquery Validation For Contact Form 7 < 5.3 - Arbitrary Options Update via CSRF — Jquery Validation For Contact Form 7 4.3 -2022-07-17
CVE-2022-1672 Insights from Google PageSpeed < 4.0.7 - Multiple CSRF — Insights from Google PageSpeed 8.8 -2022-07-17
CVE-2022-35228 SAP BusinessObjects Central Management Console 跨站请求伪造漏洞 — SAP BusinessObjects Business Intelligence Platform (Central management Console) 8.1 -2022-07-12
CVE-2022-2123 WP Opt-in <= 1.4.1 - Arbitrary Settings Update via CSRF — WP Opt-in 6.5 -2022-07-11
CVE-2022-2091 Cache Images < 3.2.1 - Image Upload / Import via CSRF — Cache Images 6.5 -2022-07-11
CVE-2022-1957 Comment License < 1.4.0 - Arbitrary Settings Update via CSRF — Comment License 4.3 -2022-07-11
CVE-2022-1956 Shortcut Macros <= 1.3 - Subscriber+ Arbitrary Settings Update — Shortcut Macros 4.3 -2022-07-11
CVE-2022-1757 Pagebar < 2.70 - Arbitrary Settings Update via CSRF to Stored XSS — pagebar 5.4 -2022-07-11
CVE-2022-1732 Rename wp-login.php <= 2.6.0 - Secret URL Update via CSRF — Rename wp-login.php 6.5 -2022-07-11
CVE-2022-1626 Sharebar <= 1.4.1 - Arbitrary Settings Update to Stored XSS via CSRF — Sharebar 4.6 -2022-07-11
CVE-2022-1599 Admin Management Xtended < 2.4.5 - Post Visibility/Date/Comment Status Update via CSRF — Admin Management Xtended 6.5 -2022-07-11
CVE-2022-1576 WP Maintenance Mode & Coming Soon < 2.4.5 - Subscribed Users Deletion via CSRF — WP Maintenance Mode & Coming Soon 6.5 -2022-07-11
CVE-2022-2353 Cross-Site Request Forgery (CSRF) in microweber/microweber — microweber/microweber 8.2 -2022-07-09
CVE-2021-23163 JFrog Artifactory 跨站请求伪造漏洞 — JFrog Artifactory 3.1 Low2022-07-06
CVE-2022-1967 WP Championship < 9.3 - Multiple CSRF — WP Championship 6.5 -2022-07-04
CVE-2017-20120 TrueConf Server cross-site request forgery — Server 4.3 Medium2022-06-29
CVE-2022-1960 MyCSS <= 1.1 - Arbitrary Settings Update via CSRF — MyCSS 4.3 -2022-06-27
CVE-2022-1914 Clean-Contact <= 1.6 - Arbitrary Settings Update to Stored XSS via CSRF — Clean-Contact 5.4 -2022-06-27
CVE-2022-1913 Add Post URL <= 2.1.0 - Arbitrary Settings Update to Stored XSS via CSRF — Add Post URL 5.4 -2022-06-27
CVE-2022-1885 Cimy Header Image Rotator <= 6.1.1 - Arbitrary Settings Update via CSRF — Cimy Header Image Rotator 4.3 -2022-06-27
CVE-2022-1847 Rotating Posts <= 1.11 - Arbitrary Settings Update to Stored XSS via CSRF — Rotating Posts 4.3 -2022-06-27
CVE-2022-1846 Tiny Contact Form <= 0.7 - Arbitrary Settings Update via CSRF — Tiny Contact Form 4.3 -2022-06-27

Vulnerabilities classified as CWE-352 (跨站请求伪造(CSRF)) represent 4776 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.