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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

4802 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-2024-10481 Cross-Site Request Forgery (CSRF) in comfyanonymous/comfyui — comfyanonymous/comfyui 8.8 -2025-03-20
CVE-2025-1314 Custom Twitter Feeds <= 2.2.5 - Cross-Site Request Forgery to Cache Reset via ctf_clear_cache_admin Function — Custom Twitter Feeds – A Tweets Widget or X Feed Widget 4.3 Medium2025-03-20
CVE-2024-13933 FoodBakery | Delivery Restaurant Directory WordPress Theme <= 4.7 - Cross-Site Request Forgery in Multiple Functions — FoodBakery | Delivery Restaurant Directory WordPress Theme 8.8 High2025-03-19
CVE-2025-2420 猫宁i Morning cross-site request forgery — Morning 4.3 Medium2025-03-17
CVE-2025-26899 WordPress Recapture for WooCommerce Plugin <= 1.0.43 - CSRF to Settings Change vulnerability — Recapture for WooCommerce 6.5 Medium2025-03-15
CVE-2025-1530 Tripetto <= 8.0.9 - Cross-Site Request Forgery to Arbitrary Results Deletion — WordPress form builder plugin for contact forms, surveys and quizzes – Tripetto 4.3 Medium2025-03-15
CVE-2024-13913 InstaWP Connect – 1-click WP Staging & Migration <= 0.1.0.83 - Cross-Site Request Forgery to Local File Inclusion — InstaWP Connect – 1-click WP Staging & Migration 8.8 High2025-03-14
CVE-2025-1764 LoginPress <= 3.3.1 - Cross-Site Request Forgery to Arbitrary Options Update — LoginPress | wp-login Custom Login Page Customizer 7.5 High2025-03-14
CVE-2025-27792 Opal vulnerable to CSRF protection bypass — opal 8.1 -2025-03-11
CVE-2025-28868 WordPress ZipList Recipe plugin <= 3.1 - Cross Site Request Forgery (CSRF) vulnerability — ZipList Recipe 4.3 Medium2025-03-11
CVE-2025-28941 WordPress SPAM-BYBYE Plugin <= 2.2.4 - Cross Site Request Forgery (CSRF) vulnerability — Spam Byebye 4.3 Medium2025-03-11
CVE-2025-28940 WordPress Back To Top Plugin <= 2.0 - Cross Site Request Forgery (CSRF) vulnerability — Back To Top 4.3 Medium2025-03-11
CVE-2025-28933 WordPress MaxA/B plugin <= 2.2.2 - CSRF to Stored XSS vulnerability — MaxA/B 7.1 High2025-03-11
CVE-2025-28932 WordPress Insert Code plugin <= 2.4 - CSRF to Stored XSS vulnerability — Insert Code 7.1 High2025-03-11
CVE-2025-28931 WordPress WordPress Hashtags plugin <= 0.3.2 - CSRF to Stored XSS vulnerability — Hashtags 7.1 High2025-03-11
CVE-2025-28927 WordPress Display Template Name plugin <= 1.7.1 - Cross Site Request Forgery (CSRF) vulnerability — Display Template Name 4.3 Medium2025-03-11
CVE-2025-28925 WordPress WATI Chat and Notification plugin <= 1.1.2 - CSRF to Stored Cross Site Scripting (XSS) vulnerability — WATI Chat and Notification 7.1 High2025-03-11
CVE-2025-28922 WordPress Go To Top plugin <= 0.0.8 - CSRF to Stored XSS vulnerability — Go To Top 7.1 High2025-03-11
CVE-2025-28923 WordPress No Disposable Email plugin <= 2.5.1 - CSRF to Stored XSS vulnerability — No Disposable Email 7.1 High2025-03-11
CVE-2025-28913 WordPress WP Add Active Class To Menu Item plugin <=1.0 - Cross Site Request Forgery (CSRF) vulnerability — WP Add Active Class To Menu Item 4.3 Medium2025-03-11
CVE-2025-28912 WordPress Custom Dashboard Page plugin <= 1.0 - Cross Site Request Forgery (CSRF) vulnerability — Custom Dashboard Page 4.3 Medium2025-03-11
CVE-2025-28910 WordPress WP Hide Admin Bar plugin <= 2.0 - Cross Site Request Forgery (CSRF) vulnerability — WP Hide Admin Bar 4.3 Medium2025-03-11
CVE-2025-28909 WordPress WP No-Bot Question plugin <= 0.1.7 - Cross Site Request Forgery (CSRF) vulnerability — WP No-Bot Question 4.3 Medium2025-03-11
CVE-2025-28902 WordPress Contact Form 7 Select Box Editor Button plugin <= 0.6 - Cross Site Request Forgery (CSRF) vulnerability — Contact Form 7 Select Box Editor Button 4.3 Medium2025-03-11
CVE-2025-28901 WordPress Members page only for logged in users plugin <= 1.4.2 - CSRF to Stored XSS vulnerability — Members page only for logged in users 7.1 High2025-03-11
CVE-2025-28900 WordPress TabGarb Pro plugin <= 2.6 - CSRF to Stored XSS vulnerability — TabGarb Pro 7.1 High2025-03-11
CVE-2025-28897 WordPress Domain Theme plugin <= 1.3 - CSRF to Stored XSS vulnerability — Domain Theme 7.1 High2025-03-11
CVE-2025-28894 WordPress List of Posts from each Category plugin for WordPress plugin <= 2.0 - CSRF to Stored XSS vulnerability — List of Posts from each Category plugin for WordPress 7.1 High2025-03-11
CVE-2025-28892 WordPress FTP Sync plugin <= 1.1.6 - CSRF to Stored XSS vulnerability — FTP Sync 7.1 High2025-03-11
CVE-2025-28891 WordPress price-calc plugin <= 0.6.3 - CSRF to Stored XSS vulnerability — price-calc 7.1 High2025-03-11

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