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-2025-31807 WordPress Product Notices for WooCommerce plugin <= 1.3.4 - Cross Site Request Forgery (CSRF) vulnerability — Product Notices for WooCommerce 4.3 Medium2025-04-01
CVE-2025-31785 WordPress Clearbit Reveal plugin <= 1.0.6 - Cross Site Request Forgery (CSRF) vulnerability — Clearbit Reveal 5.4 Medium2025-04-01
CVE-2025-31784 WordPress Embed Extended – Embed Maps, Videos, Websites, Source Codes, and more Plugin <= 1.4.0 - Cross Site Request Forgery (CSRF) vulnerability — Embed Extended 4.3 Medium2025-04-01
CVE-2025-31779 WordPress Query Wrangler plugin <= 1.5.54 - Cross Site Request Forgery (CSRF) vulnerability — Query Wrangler 5.4 Medium2025-04-01
CVE-2025-31776 WordPress Uptime Robot Plugin <= 2.3 - Cross Site Request Forgery (CSRF) vulnerability — Uptime Robot Plugin for WordPress 4.3 Medium2025-04-01
CVE-2025-31775 WordPress Google SEO Pressor for Rich snippets Plugin <= 2.0 - Cross Site Request Forgery (CSRF) vulnerability — Google SEO Pressor Snippet 4.3 Medium2025-04-01
CVE-2025-31769 WordPress CLP – Custom Login Page by NiteoThemes plugin <= 1.5.5 - Cross Site Request Forgery (CSRF) vulnerability — CLP – Custom Login Page by NiteoThemes 4.3 Medium2025-04-01
CVE-2025-31763 WordPress Cache control by Cacholong Plugin <= 5.4.1 - Cross Site Request Forgery (CSRF) vulnerability — Cache control by Cacholong 4.3 Medium2025-04-01
CVE-2025-31756 WordPress TZ PlusGallery Plugin <= 1.5.5 - Cross Site Request Forgery (CSRF) vulnerability — TZ PlusGallery 4.3 Medium2025-04-01
CVE-2025-31751 WordPress Breaking News WP Plugin <= 1.3 - CSRF to Settings Change vulnerability — Breaking News WP 6.5 Medium2025-04-01
CVE-2025-3037 yzk2356911358 StudentServlet-JSP cross-site request forgery — StudentServlet-JSP 4.3 Medium2025-03-31
CVE-2025-31690 Cache Utility - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-019 — Cache Utility 8.8 -2025-03-31
CVE-2025-31689 General Data Protection Regulation - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-018 — General Data Protection Regulation 8.8 -2025-03-31
CVE-2025-31688 Configuration Split - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-017 — Configuration Split 8.8 -2025-03-31
CVE-2025-31684 OAuth2 Client - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-013 — OAuth2 Client 8.8 -2025-03-31
CVE-2025-31683 Google Tag - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-012 — Google Tag 8.8 -2025-03-31
CVE-2025-31680 Matomo Analytics - Moderately critical - Cross site request forgery - SA-CONTRIB-2025-008 — Matomo Analytics 8.8 -2025-03-31
CVE-2025-31677 AI (Artificial Intelligence) - Critical - Cross Site Request Forgery - SA-CONTRIB-2025-003 — AI (Artificial Intelligence) 8.8 -2025-03-31
CVE-2025-29929 Tuleap is missing CSRF protection on tracker hierarchy administration — tuleap 4.6 Medium2025-03-31
CVE-2025-29766 Tuleap has missing CSRF protections on artifact submission & edition from the tracker view — tuleap 4.6 Medium2025-03-31
CVE-2025-31623 WordPress Rich Text Editor plugin <= 1.0.1 - CSRF to Stored XSS vulnerability — Rich Text Editor 7.1 High2025-03-31
CVE-2025-31617 WordPress PostmarkApp Email Integrator plugin <= 2.4 - CSRF to Stored XSS vulnerability — PostmarkApp Email Integrator 7.1 High2025-03-31
CVE-2025-31616 WordPress Varnish WordPress plugin <= 1.7 - CSRF to Stored XSS vulnerability — Varnish WordPress 7.1 High2025-03-31
CVE-2025-31613 WordPress AB Google Map Travel plugin <= 4.6 - CSRF to Stored XSS vulnerability — AB Google Map Travel 7.1 High2025-03-31
CVE-2025-31602 WordPress Apimo Connector plugin <= 2.6.5.1 - Cross Site Request Forgery (CSRF) vulnerability — Apimo Connector 4.3 Medium2025-03-31
CVE-2025-31601 WordPress Appointy Appointment Scheduler plugin <= 4.2.1 - CSRF to Settings Change vulnerability — Appointy Appointment Scheduler 6.5 Medium2025-03-31
CVE-2025-31600 WordPress DesignO plugin <= 2.6.0 - Cross Site Request Forgery (CSRF) vulnerability — DesignO 4.3 Medium2025-03-31
CVE-2025-31588 WordPress Elfsight Testimonials Slider plugin <= 1.0.1 - Cross Site Request Forgery (CSRF) to Settings Change vulnerability — Elfsight Testimonials Slider 5.4 Medium2025-03-31
CVE-2025-31585 WordPress Leadfox for WordPress plugin <= 2.1.9 - CSRF to Stored XSS vulnerability — Leadfox for WordPress 7.1 High2025-03-31
CVE-2025-31583 WordPress WP Copy Media URL plugin <= 2.1 - CSRF to Stored XSS vulnerability — WP Copy Media URL 7.1 High2025-03-31

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