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-32732 Cross-Site Request Forgery in xwiki-platform — xwiki-platform 7.5 High2022-02-04
CVE-2021-25092 Link Library < 7.2.8 - Library Settings Reset via CSRF — Link Library 6.5 -2022-02-01
CVE-2021-25072 NextScripts: Social Networks Auto-Poster < 4.3.25 - Arbitrary Post Deletion via CSRF — NextScripts: Social Networks Auto-Poster 6.5 -2022-02-01
CVE-2021-24761 Error Log Viewer < 1.1.2 - Arbitrary Text File Deletion via CSRF — Error Log Viewer by BestWebSoft 6.5 -2022-02-01
CVE-2022-23601 CSRF token missing in Symfony — symfony 8.1 High2022-02-01
CVE-2021-25097 LabTools <= 1.0 - Subscriber+ Arbitrary Publication Deletion — LabTools 6.5 -2022-02-01
CVE-2022-0335 Moodle 跨站请求伪造漏洞 — moodle 8.8 -2022-01-25
CVE-2022-0269 Cross-Site Request Forgery (CSRF) in yetiforcecompany/yetiforcecrm — yetiforcecompany/yetiforcecrm 8.1 -2022-01-24
CVE-2021-25073 WP125 < 1.5.5 - Arbitrary Ad Deletion via CSRF — WP125 6.5 -2022-01-24
CVE-2021-24989 Accept Donations with PayPal < 1.3.4 - Arbitrary Post Deletion via CSRF — Accept Donations with PayPal 6.5 -2022-01-24
CVE-2021-24936 WP Extra File Types < 0.5.1 - CSRF to Stored Cross-Site Scripting — WP Extra File Types 8.2 -2022-01-24
CVE-2021-24696 Simple Download Monitor < 3.9.9 - Multiple CSRF — Simple Download Monitor 8.8 -2022-01-24
CVE-2021-44777 WordPress Email Tracker plugin <= 5.2.6 - Cross-Site Request Forgery (CSRF) vulnerabilities leading to single or bulk e-mail entries deletion — Email Tracker (WordPress plugin) 5.4 Medium2022-01-19
CVE-2022-0215 XootiX Plugins <= Various Versions Cross-Site Request Forgery to Arbitrary Options Update — Login/Signup Popup 8.8 High2022-01-18
CVE-2021-43353 Crisp Live Chat <= 0.31 Cross-Site Request Forgery to Stored Cross-Site Scripting — Crisp Live Chat 8.8 High2022-01-18
CVE-2022-0245 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 6.5 -2022-01-18
CVE-2021-4164 Cross-Site Request Forgery (CSRF) in janeczku/calibre-web — janeczku/calibre-web 8.1 -2022-01-17
CVE-2021-25025 Event Calendar < 1.1.51 - Subscriber+ Event Creation — EventCalendar 4.3 -2022-01-17
CVE-2022-0238 Cross-Site Request Forgery (CSRF) in phoronix-test-suite/phoronix-test-suite — phoronix-test-suite/phoronix-test-suite 4.3 -2022-01-16
CVE-2022-0226 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 4.3 -2022-01-14
CVE-2022-0231 Cross-Site Request Forgery (CSRF) in livehelperchat/livehelperchat — livehelperchat/livehelperchat 4.3 -2022-01-14
CVE-2021-23227 WordPress PHP Everywhere Plugin <= 2.0.2 is vulnerable to Cross Site Request Forgery (CSRF) — PHP Everywhere (WordPress plugin) 5.4 Medium2022-01-13
CVE-2022-0196 Cross-Site Request Forgery (CSRF) in phoronix-test-suite/phoronix-test-suite — phoronix-test-suite/phoronix-test-suite 4.3 -2022-01-13
CVE-2022-0197 Cross-Site Request Forgery (CSRF) in phoronix-test-suite/phoronix-test-suite — phoronix-test-suite/phoronix-test-suite 4.3 -2022-01-13
CVE-2021-37198 Siemens Comos 跨站请求伪造漏洞 — COMOS V10.2 8.8 -2022-01-11
CVE-2021-25052 Button Generator < 2.3.3 - RFI leading to RCE via CSRF — Button Generator – easily Button Builder 8.8 -2022-01-10
CVE-2021-25053 WP Coder < 2.5.2 - RFI leading to RCE via CSRF — WP Coder – add custom html, css and js code 8.8 -2022-01-10
CVE-2021-25051 Modal Window < 5.2.2 - RFI leading to RCE via CSRF — Modal Window – create popup modal window 8.8 -2022-01-10
CVE-2021-25032 PublishPress Capabilities < 2.3.1 - Unauthenticated Arbitrary Options Update to Blog Compromise — PublishPress Capabilities – User Role Access, Editor Permissions, Admin Menus 9.8 -2022-01-10
CVE-2021-4168 Cross-Site Request Forgery (CSRF) in star7th/showdoc — star7th/showdoc 6.5 -2021-12-26

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