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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

4777 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-2021-4162 Cross-Site Request Forgery (CSRF) in archivy/archivy — archivy/archivy 4.3 -2021-12-25
CVE-2021-36886 WordPress Contact Form 7 Database Addon – CFDB7 plugin <= 1.2.5.9 - Cross-Site Request Forgery (CSRF) vulnerability — Contact Form 7 Database Addon – CFDB7 (WordPress plugin) 6.5 Medium2021-12-22
CVE-2021-43846 CSRF forgery protection bypass for Spree::OrdersController#populate — solidus 5.3 Medium2021-12-20
CVE-2021-36887 WordPress tarteaucitron.js – Cookies legislation & GDPR plugin <= 1.5.4 - Cross-Site Request Forgery (CSRF) vulnerability leading to Cross-Site Scripting (XSS) — tarteaucitron.js – Cookies legislation & GDPR (WordPress plugin) 6.1 Medium2021-12-20
CVE-2021-4131 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 4.3 -2021-12-18
CVE-2021-4130 Cross-Site Request Forgery (CSRF) in snipe/snipe-it — snipe/snipe-it 4.3 -2021-12-18
CVE-2021-41260 Missing CSRF checks in Galette — galette 8.2 High2021-12-16
CVE-2021-4123 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 4.3 -2021-12-16
CVE-2021-24922 Pixel Cat Lite < 2.6.2 - CSRF to Stored Cross-Site Scripting — Pixel Cat – Conversion Pixel Manager 8.2 -2021-12-13
CVE-2021-24818 WP Limits <= 1.0 - Plugin's Settings Update via CSRF — Wp Limits 4.3 -2021-12-13
CVE-2021-24795 Filter Portfolio Gallery <= 1.5 - Arbitrary Gallery Deletion via CSRF — Filter Portfolio Gallery 6.5 -2021-12-13
CVE-2021-24784 WP Admin Logo Changer <= 1.0 - Plugin's Settings Update via CSRF — WP Admin Logo Changer 6.5 -2021-12-13
CVE-2021-24780 Single Post Exporter <= 1.1.1 - Plugin's Settings Update via CSRF — Single Post Exporter 4.3 -2021-12-13
CVE-2021-4092 Cross-Site Request Forgery (CSRF) in yetiforcecompany/yetiforcecrm — yetiforcecompany/yetiforcecrm 4.3 -2021-12-11
CVE-2021-4082 Cross-Site Request Forgery (CSRF) in pimcore/pimcore — pimcore/pimcore 4.3 -2021-12-10
CVE-2021-4033 Cross-Site Request Forgery (CSRF) in kevinpapst/kimai2 — kevinpapst/kimai2 4.3 -2021-12-09
CVE-2021-4049 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 4.3 -2021-12-07
CVE-2021-35242 A valid CSRF token is present in response to an invalid request — Serv-U Server 8.3 High2021-12-06
CVE-2021-4005 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-12-04
CVE-2021-3944 Cross-Site Request Forgery (CSRF) in bookstackapp/bookstack — bookstackapp/bookstack 6.5 -2021-12-02
CVE-2021-3993 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-12-01
CVE-2021-4015 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-12-01
CVE-2021-4017 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-12-01
CVE-2021-42364 Stetic <= 1.0.6 Cross-Site Request Forgery to Stored Cross-Site Scripting — Stetic 8.8 High2021-11-29
CVE-2021-42358 Contact Form With Captcha <= 1.6.2 Cross-Site Request Forgery to Reflected Cross-Site Scripting — Contact Form With Captcha 8.8 High2021-11-29
CVE-2021-24749 URL Shortify < 1.5.1 - Arbitrary Link/Group Deletion via CSRF — URL Shortify – Simple, Powerful and Easy URL Shortener Plugin For WordPress 6.5 -2021-11-29
CVE-2021-43777 Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce) — redash 6.8 Medium2021-11-23
CVE-2021-24668 MAZ Loader < 1.4.1 - Arbitrary Loader Deletion via CSRF — MAZ Loader – Preloader Builder for WordPress 6.5 -2021-11-23
CVE-2021-24641 Images to WebP < 1.9 - Multiple Cross Site Request Forgery (CSRF) — Images to WebP 8.1 -2021-11-23
CVE-2021-43559 Moodle 跨站请求伪造漏洞 — moodle 8.8 -2021-11-22

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