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-34358 CSRF Vulnerability in QmailAgent — QmailAgent 6.8 Medium2021-11-20
CVE-2021-39198 The disqualify lead action may be executed without CSRF token check — crm 4.2 Medium2021-11-19
CVE-2021-39353 Easy Registration Forms <= 2.1.1 Cross-Site Request Forgery to Stored Cross-Site Scripting — Easy Registration Forms 8.8 High2021-11-19
CVE-2021-3957 Cross-Site Request Forgery (CSRF) in kevinpapst/kimai2 — kevinpapst/kimai2 4.3 -2021-11-19
CVE-2021-3963 Cross-Site Request Forgery (CSRF) in kevinpapst/kimai2 — kevinpapst/kimai2 4.3 -2021-11-19
CVE-2021-3976 Cross-Site Request Forgery (CSRF) in kevinpapst/kimai2 — kevinpapst/kimai2 4.3 -2021-11-19
CVE-2021-36908 WordPress WP Reset PRO Premium Plugin <= 5.98 - Cross-Site Request Forgery (CSRF) vulnerability — WP Reset PRO 8.8 High2021-11-18
CVE-2021-41274 Authentication Bypass by CSRF Weakness — solidus_auth_devise 9.3 Critical2021-11-17
CVE-2021-41275 Authentication Bypass by CSRF Weakness — spree_auth_devise 9.3 Critical2021-11-17
CVE-2021-41273 Cross-Site Request Forgery allowing sending of test emails and generation of node auto-deployment keys — panel 4.3 Medium2021-11-17
CVE-2021-24852 MouseWheel Smooth Scroll < 5.7 - Plugin's Setting Update via CSRF — MouseWheel Smooth Scroll 6.5 -2021-11-17
CVE-2021-24804 Simple JWT Login < 3.2.1 - Arbitrary Settings Update to Site Takeover via CSRF — Simple JWT Login – Login and Register to WordPress using JWT 8.8 -2021-11-17
CVE-2021-24802 Colorful Categories < 2.0.15 - Arbitrary Colors Update via CSRF — Colorful Categories 4.3 -2021-11-17
CVE-2021-24776 WP Performance Score Booster < 2.1 - Settings Change via CSRF — WP Performance Score Booster – Optimize Speed, Enable Cache & Page Preload 4.3 -2021-11-17
CVE-2021-25965 Calibre-web - Admin Account Takeover via Cross-Site Request Forgery (CSRF) — calibreweb 8.8 High2021-11-16
CVE-2021-25976 Piranha CMS - Site-wide Cross-Site Request Forgery (CSRF) — Piranha 8.1 High2021-11-16
CVE-2021-3683 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-11-13
CVE-2021-3775 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-11-13
CVE-2021-3776 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-11-13
CVE-2021-3921 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-11-13
CVE-2021-3931 Cross-Site Request Forgery (CSRF) in snipe/snipe-it — snipe/snipe-it 4.3 -2021-11-13
CVE-2021-3932 Cross-Site Request Forgery (CSRF) in area17/twill — area17/twill 4.3 -2021-11-13
CVE-2021-24832 WP SEO Redirect 301 < 2.3.2 - Redirect Deletion via CSRF — WP SEO Redirect 301 6.5 -2021-11-08
CVE-2021-24806 wpDiscuz < 7.3.4 - Arbitrary Comment Addition/Edition/Deletion via CSRF — Comments – wpDiscuz 6.5 -2021-11-08
CVE-2021-24767 Redirect 404 Error Page to Homepage or Custom Page with Logs < 1.7.9 - Log Deletion via CSRF — Redirect 404 Error Page to Homepage or Custom Page with Logs 6.5 -2021-11-08
CVE-2021-24766 404 to 301 < 3.0.9 - Logs Deletion via CSRF — 404 to 301 – Redirect, Log and Notify 404 Errors 4.3 -2021-11-08
CVE-2021-24674 Genie WP Favicon <= 0.5.2 - Arbitrary Favicon Change via CSRF — Genie WP Favicon 6.5 -2021-11-08
CVE-2021-34773 Cisco Unified Communications Products Cross-Site Request Forgery Vulnerability — Cisco Unified Communications Manager 6.5 Medium2021-11-04
CVE-2021-24809 BP Better Messages < 1.9.9.41 - Multiple CSRF — BP Better Messages 8.8 -2021-11-01
CVE-2021-24799 Far Future Expiry Header < 1.5 - Plugin's Settings Update via CSRF — Far Future Expiry Header 4.3 -2021-11-01

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