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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

4907 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-4404 Event Espresso 4 Decaf <= 4.10.11 - Cross-Site Request Forgery Bypass — Event Espresso – Event Registration & Ticketing Sales 4.3 Medium2023-07-01
CVE-2021-4403 Remove Schema <= 1.5 - Cross-Site Request Forgery Bypass — Remove Schema 4.3 Medium2023-07-01
CVE-2020-36748 Dokan <= 3.0.8 - Cross-Site Request Forgery Bypass — Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy 4.3 Medium2023-07-01
CVE-2021-4402 Multiple Roles <= 1.3.1- Cross-Site Request Forgery Bypass — Multiple Roles 4.3 Medium2023-07-01
CVE-2020-36747 Lightweight Sidebar Manager <= 1.1.4 - Cross-Site Request Forgery Bypass — Lightweight Sidebar Manager 4.3 Medium2023-07-01
CVE-2021-4401 Style Kits <= 1.8.0 - Cross-Site Request Forgery Bypass — Style Kits – Advanced Theme Styles for Elementor, Elementor Kits & Elementor Patterns 8.8 High2023-07-01
CVE-2021-4400 Better Search <= 2.5.2 - Cross-Site Request Forgery Bypass — Better Search – Relevant search results for WordPress 4.3 Medium2023-07-01
CVE-2021-4399 Edwiser Bridge <= 2.0.6 - Cross-Site Request Forgery Bypass — Edwiser Bridge – WordPress Moodle Integration 4.3 Medium2023-07-01
CVE-2021-4398 Amministrazione Trasparente <= 7.1 - Cross-Site Request Forgery Bypass — Amministrazione Trasparente 4.3 Medium2023-07-01
CVE-2021-4397 Staff Directory Plugin <= 3.6 - Cross-Site Request Forgery Bypass — Staff Directory Plugin: Company Directory 4.3 Medium2023-07-01
CVE-2021-4396 Rucy <= 0.4.4 - Cross-Site Request Forgery Bypass — Rucy 4.3 Medium2023-07-01
CVE-2020-36746 Menu Swapper <= 1.1.0.2 - Cross-Site Request Forgery Bypass — Menu Swapper 4.3 Medium2023-07-01
CVE-2021-4395 Abandoned Cart Recovery for WooCommerce <= 1.0.4 - Cross-Site Request Forgery Bypass — Abandoned Cart Recovery for WooCommerce 4.3 Medium2023-07-01
CVE-2020-36745 WP Project Manager <= 2.4.0 - Cross-Site Request Forgery Bypass — Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker 4.3 Medium2023-07-01
CVE-2021-4394 Locations <= 3.2.1 - Cross-Site Request Forgery Bypass — Locations 4.3 Medium2023-07-01
CVE-2020-36744 NotificationX <= 1.8.2 - Cross-Site Request Forgery Bypass — NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar 4.3 Medium2023-07-01
CVE-2021-4392 eCommerce Product Catalog Plugin for WordPress <= 2.9.43 - Cross-Site Request Forgery Bypass — eCommerce Product Catalog Plugin for WordPress 4.3 Medium2023-07-01
CVE-2020-36743 Product Catalog Simple <= 1.5.13 - Cross-Site Request Forgery Bypass — Product Catalog Simple 4.3 Medium2023-07-01
CVE-2020-36742 Custom Field Template <= 2.5.1 - Cross-Site Request Forgery Bypass — Custom Field Template 4.3 Medium2023-07-01
CVE-2021-4391 Ultimate Gift Cards for WooCommerce <= 2.1.1 - Cross-Site Request Forgery Bypass — Ultimate Gift Cards for WooCommerce 4.3 Medium2023-07-01
CVE-2020-36741 MultiVendorX – MultiVendor Marketplace Solution For WooCommerce <= 3.5.7 - Cross-Site Request Forgery Bypass — MultiVendorX – WooCommerce Multivendor Marketplace Solutions 4.3 Medium2023-07-01
CVE-2021-4390 Contact Form 7 Style <= 3.2 - Cross-Site Request Forgery Bypass — Contact Form 7 Style 4.3 Medium2023-07-01
CVE-2021-4389 WP Travel <= 4.4.6 - Cross-Site Request Forgery Bypass — WP Travel – Ultimate Travel Booking System, Tour Management Engine 4.3 Medium2023-07-01
CVE-2020-36740 Radio Buttons for Taxonomies <= 2.0.5 - Cross-Site Request Forgery Bypass — Radio Buttons for Taxonomies 4.3 Medium2023-07-01
CVE-2021-4393 eCommerce Product Catalog Plugin for WordPress <= 3.0.17 - Cross-Site Request Forgery Bypass — eCommerce Product Catalog Plugin for WordPress 4.3 Medium2023-07-01
CVE-2021-4387 Opal Estate <= 1.6.11 - Cross-Site Request Forgery Bypass — Opal Estate 4.3 Medium2023-07-01
CVE-2021-4386 WP Security Question <= 1.0.5 - Cross-Site Request Forgery Bypass — WP Security Question 4.3 Medium2023-07-01
CVE-2021-4385 WP Private Content Plus <= 3.1 - Cross-Site Request Forgery Bypass — WP Private Content Plus 4.3 Medium2023-07-01
CVE-2020-36739 Feed Them Social – Page, Post, Video, and Photo Galleries <= 2.8.6 - Cross-Site Request Forgery Bypass — Feed Them Social – Social Media Feeds, Video, and Photo Galleries 4.3 Medium2023-07-01
CVE-2020-36738 Cool Timeline (Horizontal & Vertical Timeline) <= 2.0.2 - Cross-Site Request Forgery Bypass — Cool Timeline (Horizontal & Vertical Timeline) 4.3 Medium2023-07-01

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