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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

4911 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-2023-6492 Simple Sitemap <= 3.5.13 - Cross-Site Request Forgery via admin_notices — Simple Sitemap – Create a Responsive HTML Sitemap 4.3 Medium2024-06-14
CVE-2024-0892 Schema App Structured Data <= 2.2.0 - Cross-Site Request Forgery — Schema App Structured Data 4.3 Medium2024-06-14
CVE-2024-37306 CVAT's export and backup-related API endpoints are susceptible to CSRF — cvat 7.1 High2024-06-13
CVE-2023-47845 WordPress Grab & Save plugin <= 1.0.4 - Cross-Site Request Forgery (CSRF) vulnerability — Grab & Save 4.3 Medium2024-06-12
CVE-2024-35207 Siemens SINEC Traffic Analyzer 跨站请求伪造漏洞 — SINEC Traffic Analyzer 7.8 High2024-06-11
CVE-2024-4403 CSRF in restart_program in parisneo/lollms-webui — parisneo/lollms-webui 8.1 -2024-06-10
CVE-2024-5786 Cross-Site Request Forgery vulnerability in Comtrend router — Comtrend WLD71-T1_v2.0.201820 6.5 Medium2024-06-10
CVE-2024-4328 CSRF in clear_personality_files_list in parisneo/lollms-webui — parisneo/lollms-webui 8.1 -2024-06-10
CVE-2024-35657 WordPress WP-Recall plugin <= 16.26.6 - Cross Site Request Forgery (CSRF) vulnerability — WP-Recall 5.4 Medium2024-06-08
CVE-2024-35684 WordPress ElasticPress plugin <= 5.1.1 - Cross Site Request Forgery (CSRF) vulnerability — ElasticPress 4.3 Medium2024-06-08
CVE-2024-35689 WordPress Analytify plugin <= 5.2.3 - Cross Site Request Forgery (CSRF) vulnerability — Analytify 5.4 Medium2024-06-08
CVE-2024-2288 CSRF File Upload Vulnerability in parisneo/lollms-webui — parisneo/lollms-webui 7.1AIHighAI2024-06-06
CVE-2024-1879 CSRF to RCE in significant-gravitas/autogpt — significant-gravitas/autogpt 8.8AIHighAI2024-06-06
CVE-2024-35673 WordPress Pure Chat plugin <= 2.22 - Cross Site Request Forgery (CSRF) vulnerability — Pure Chat 4.3 Medium2024-06-05
CVE-2024-2368 Mollie Forms <= 2.6.13 - Cross-Site Request Forgery to Arbitrary Post Duplication — Mollie Forms 4.3 Medium2024-06-05
CVE-2024-35632 WordPress Integration for Constant Contact and Contact Form 7, WPForms, Elementor, Ninja Forms plugin <= 1.1.5 - Cross Site Request Forgery (CSRF) vulnerability — Integration for Contact Form 7 and Constant Contact 4.3 Medium2024-06-03
CVE-2024-35638 WordPress ActiveDEMAND plugin <= 0.2.43 - Cross Site Request Forgery (CSRF) vulnerability — ActiveDEMAND 4.3 Medium2024-06-03
CVE-2024-4344 Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 19.1.13 - Cross-Site Request Forgery — Shield: Blocks Bots, Protects Users, and Prevents Security Breaches 4.3 Medium2024-06-02
CVE-2024-35636 WordPress Uploadcare File Uploader and Adaptive Delivery plugin <= 3.0.11 - Cross Site Request Forgery (CSRF) vulnerability — Uploadcare File Uploader and Adaptive Delivery (beta) 4.3 Medium2024-06-01
CVE-2024-34008 moodle: CSRF risk in analytics management of models 8.8 -2024-05-31
CVE-2024-34007 moodle: logout CSRF in admin/tool/mfa/auth.php 8.8 -2024-05-31
CVE-2024-34001 moodle: CSRF risk in admin preset tool management of presets 8.8 -2024-05-31
CVE-2024-4426 Comparison Slider <= 1.0.5 - Cross-Site Request Forgery — Comparison Slider 4.3 Medium2024-05-30
CVE-2024-3947 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_settings — WP To Do 4.3 Medium2024-05-30
CVE-2024-3945 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_manage() — WP To Do 4.3 Medium2024-05-30
CVE-2024-3943 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment — WP To Do 4.3 Medium2024-05-30
CVE-2024-4218 AffiEasy <= 1.1.6 - Cross-Site Request Forgery to Various Actions — AffiEasy 6.5 Medium2024-05-30
CVE-2024-5185 Data Poisoning in EmbedAI — EmbedAI 7.3 High2024-05-29
CVE-2024-4429 Cross Site Request Forgery vulnerability in iManager — iManager 5.4 Medium2024-05-28
CVE-2024-5428 SourceCodester Simple Online Bidding System HTTP POST Request save_product cross-site request forgery — Simple Online Bidding System 4.3 Medium2024-05-28

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