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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

4795 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-4707 Royal Elementor Addons <= 1.3.59 - Cross-Site Request Forgery to Menu Template creation — Royal Addons for Elementor – Addons and Templates Kit for Elementor 4.3 Medium2023-01-10
CVE-2023-22472 Nextcloud Deck Desktop Client is vulnerable to Cross-Site Request Forgery (CSRF) via malicious link — security-advisories 5.3 Medium2023-01-09
CVE-2023-0088 Swifty Page Manager <= 3.0.1 - Cross-Site Request Forgery — Swifty Page Manager 8.8 High2023-01-05
CVE-2023-0086 JetWidgets for Elementor <= 1.0.12 - Cross-Site Request Forgery to Settings Update — JetWidgets For Elementor 5.4 Medium2023-01-05
CVE-2016-15009 OpenACS bug-tracker Search nav-bar.adp cross-site request forgery — bug-tracker 3.5 Low2023-01-05
CVE-2023-22457 org.xwiki.contrib:application-ckeditor-ui vulnerable to Remote Code Execution via Cross-Site Request Forgery — application-ckeditor 9.1 Critical2023-01-04
CVE-2022-42435 IBM Business Automation Workflow cross-site request forgery — Business Automation Workflow 4.3 Medium2023-01-03
CVE-2014-125028 valtech IDP Test Client main.py cross-site request forgery — IDP Test Client 4.3 Medium2022-12-31
CVE-2022-4867 Cross-Site Request Forgery (CSRF) in froxlor/froxlor — froxlor/froxlor 4.3 -2022-12-31
CVE-2022-4844 Cross-Site Request Forgery (CSRF) in usememos/memos — usememos/memos 6.5 -2022-12-29
CVE-2022-4845 Cross-Site Request Forgery (CSRF) in usememos/memos — usememos/memos 6.5 -2022-12-29
CVE-2022-4846 Cross-Site Request Forgery (CSRF) in usememos/memos — usememos/memos 6.5 -2022-12-29
CVE-2022-4849 Cross-Site Request Forgery (CSRF) in usememos/memos — usememos/memos 6.5 -2022-12-29
CVE-2022-4850 Cross-Site Request Forgery (CSRF) in usememos/memos — usememos/memos 6.5 -2022-12-29
CVE-2022-4766 dolibarr_project_timesheet Form cross-site request forgery — dolibarr_project_timesheet 4.3 Medium2022-12-27
CVE-2020-36633 moodle-block_sitenews block_sitenews.php get_content cross-site request forgery — moodle-block_sitenews 4.3 Medium2022-12-27
CVE-2022-4646 Cross-Site Request Forgery (CSRF) in ikus060/rdiffweb — ikus060/rdiffweb 7.1 -2022-12-22
CVE-2022-4633 Auto Upload Images Settings setting-page.php cross-site request forgery — Auto Upload Images 4.3 Medium2022-12-21
CVE-2022-4604 wp-english-wp-admin Plugin english-wp-admin.php register_endpoints cross-site request forgery — wp-english-wp-admin Plugin 4.3 Medium2022-12-18
CVE-2022-4564 University of Central Florida Materia API Controller api.php before cross-site request forgery — Materia 4.3 Medium2022-12-16
CVE-2022-3427 Corner Ad <= 1.0.56 - Cross-Site Request Forgery — Corner Ad 8.8 High2022-12-15
CVE-2022-41263 SAP Business Objects Business Intelligence Platform 跨站请求伪造漏洞 — Business Objects Business Intelligence Platform (Web intelligence) 4.3 Medium2022-12-12
CVE-2022-41622 iControl SOAP vulnerability — BIG-IP 8.8 High2022-12-07
CVE-2022-45824 WordPress Advanced Booking Calendar Plugin <= 1.7.1 is vulnerable to Cross Site Request Forgery (CSRF) — Advanced Booking Calendar 5.4 Medium2022-12-05
CVE-2022-35730 WordPress Oceanwp sticky header plugin <= 1.0.8 is vulnerable to Cross Site Request Forgery (CSRF) — Oceanwp sticky header 4.3 Medium2022-12-04
CVE-2022-4220 Chained Quiz <= 1.3.2.4 - Cross-Site Request Forgery to Question Deletion — Chained Quiz 5.4 Medium2022-12-02
CVE-2022-4219 Chained Quiz <= 1.3.2.4 - Cross-Site Request Forgery to Submitted Response Deletion — Chained Quiz 5.4 Medium2022-12-02
CVE-2022-4218 Chained Quiz <= 1.3.2.4 - Cross-Site Request Forgery to Arbitrary Quiz Deletion and Copying — Chained Quiz 5.4 Medium2022-12-02
CVE-2022-41297 IBM Db2U cross-site request forgery — Db2U 4.3 Medium2022-12-01
CVE-2022-41296 IBM Db2U cross-site respect forgery — Db2U 6.5 Medium2022-12-01

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