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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

4776 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-1591 WordPress Ping Optimizer < 2.35.1.3.0 - Arbitrary Settings Update via CSRF — WordPress Ping Optimizer 4.3 -2022-09-19
CVE-2022-3232 Cross-Site Request Forgery (CSRF) in ikus060/rdiffweb — ikus060/rdiffweb 7.1 -2022-09-17
CVE-2022-29489 WordPress Sucuri Security plugin <= 1.8.33 - Cross-Site Request Forgery (CSRF) vulnerability — Sucuri Security (WordPress plugin) 4.3 -2022-09-16
CVE-2022-3221 Cross-Site Request Forgery (CSRF) in ikus060/rdiffweb — ikus060/rdiffweb 7.1 -2022-09-15
CVE-2022-40623 WAVLINK Quantum D4G (WN531G3) CSRF — WN531G3 8.8 -2022-09-13
CVE-2022-38139 WordPress RD Station plugin <= 5.2.0 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities — RD Station (WordPress plugin) 5.4 Medium2022-09-13
CVE-2022-35277 WordPress GetResponse plugin <= 5.5.20 - Cross-Site Request Forgery (CSRF) vulnerability — GetResponse for WordPress (WordPress plugin) 5.4 Medium2022-09-09
CVE-2022-37411 WordPress Captcha Code plugin <= 2.7 - Cross-Site Request Forgery (CSRF) vulnerability — Captcha Code (WordPress plugin) 5.4 Medium2022-09-09
CVE-2022-37405 WordPress Better Font Awesome plugin <= 2.0.1 - Cross-Site Request Forgery (CSRF) vulnerability — Better Font Awesome (WordPress plugin) 4.3 Medium2022-09-09
CVE-2022-38093 WordPress All in One SEO plugin <= 4.2.3.1 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities — All in One SEO (WordPress plugin) 5.4 Medium2022-09-09
CVE-2022-38144 WordPress wpForo Forum plugin <= 2.0.5 - Cross-Site Request Forgery (CSRF) vulnerability — wpForo Forum (WordPress plugin) 8.8 -2022-09-09
CVE-2022-38059 WordPress Access Code Feeder plugin <= 1.0.3 - Cross-Site Request Forgery (CSRF) vulnerability — Access Code Feeder (WordPress plugin) 5.5 Medium2022-09-09
CVE-2022-36095 XWiki Cross-Site Request Forgery (CSRF) for actions on tags — xwiki-platform 4.3 Medium2022-09-08
CVE-2022-2540 Link Optimizer Lite <= 1.4.5 - Cross-Site Request Forgery to Cross-Site Scripting — Link Optimizer Lite 8.8 High2022-09-06
CVE-2022-2541 uContext for Amazon <= 3.9.1 - Cross-Site Request Forgery to Cross-Site Scripting — uContext for Amazon 8.8 High2022-09-06
CVE-2022-2542 uContext for Clickbank <= 3.9.1 - Cross-Site Request Forgery to Cross-Site Scripting — uContext for Clickbank 8.8 High2022-09-06
CVE-2022-2518 Stockists Manager for Woocommerce <= 1.0.2.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting — Stockists Manager for Woocommerce 8.8 High2022-09-06
CVE-2022-2432 Ecwid Ecommerce Shopping Cart <= 6.10.23 - Cross-Site Request Forgery to Settings/Options Update — Ecwid Ecommerce Shopping Cart 8.8 High2022-09-06
CVE-2022-2233 Banner Cycler <= 1.4 - Cross-Site Request Forgery to Cross-Site Scripting — Banner Cycler 8.8 High2022-09-06
CVE-2022-33177 WordPress Booking Calendar plugin <= 9.2.1 - Cross-Site Request Forgery (CSRF) vulnerabiulity — Booking Calendar (WordPress plugin) 5.4 Medium2022-09-06
CVE-2022-3121 SourceCodester Online Employee Leave Management System addemployee.php cross-site request forgery — Online Employee Leave Management System 4.3 Medium2022-09-05
CVE-2022-36076 Account takeover via SSO plugins in NodeBB — NodeBB 8.8 High2022-09-02
CVE-2022-36373 WordPress MP3 jPlayer plugin <= 2.7.3 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities — MP3-jPlayer (WordPress plugin) 5.4 Medium2022-09-01
CVE-2022-36796 WordPress CallRail Phone Call Tracking plugin <= 0.4.9 - Cross-Site Request Forgery (CSRF) vulnerability leading to Stored Cross-Site Scripting (XSS) — CallRail Phone Call Tracking (WordPress plugin) 6.1 Medium2022-09-01
CVE-2022-3017 Cross-Site Request Forgery (CSRF) in froxlor/froxlor — froxlor/froxlor 7.1 -2022-08-28
CVE-2022-36358 WordPress SEO Scout plugin <= 0.9.83 - Cross-Site Request Forgery (CSRF) vulnerability — SEO Scout 5.4 Medium2022-08-25
CVE-2022-36389 WordPress Better Messages plugin <= 1.9.9.148 - Cross-Site Request Forgery (CSRF) vulnerability — Better Messages (WordPress plugin) 4.3 Medium2022-08-23
CVE-2022-36292 WordPress Gallery PhotoBlocks plugin <= 1.2.6 - Cross-Site Request Forgery (CSRF) vulnerabilities — Gallery PhotoBlocks (WordPress plugin) 5.4 Medium2022-08-23
CVE-2022-36379 WordPress ЮKassa для WooCommerce plugin <= 2.3.0 - Cross-Site Request Forgery (CSRF) leading to plugin settings update — ЮKassa для WooCommerce (WordPress plugin) 8.8 High2022-08-23
CVE-2022-36288 WordPress Download Manager plugin <= 3.2.48 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities — Download Manager (WordPress plugin) 5.4 Medium2022-08-23

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