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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

4920 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-47685 WordPress Preloader Matrix Plugin <= 2.0.1 is vulnerable to Cross Site Request Forgery (CSRF) — Preloader Matrix 5.4 Medium2023-11-18
CVE-2023-5444 CSRF in ePO leading to privilege escalation — ePolicy Orchestrator 8.0 High2023-11-17
CVE-2023-47686 WordPress Arigato Autoresponder and Newsletter Plugin <= 2.7.2.2 is vulnerable to Cross Site Request Forgery (CSRF) — Arigato Autoresponder and Newsletter 4.3 Medium2023-11-16
CVE-2023-47687 WordPress Woo Custom and Sequential Order Number Plugin <= 2.6.0 is vulnerable to Cross Site Request Forgery (CSRF) — Woo Custom and Sequential Order Number 4.3 Medium2023-11-16
CVE-2023-47688 WordPress Youtube SpeedLoad Plugin <= 0.6.3 is vulnerable to Cross Site Request Forgery (CSRF) — Youtube SpeedLoad 4.3 Medium2023-11-16
CVE-2023-6022 Cross-Site Request Forgery (CSRF) in prefecthq/prefect — prefecthq/prefect 8.8 -2023-11-16
CVE-2023-4690 Elementor Addon Elements <= 1.12.7 - Cross-Site Request Forgery — Addon Elements for Elementor (formerly Elementor Addon Elements) 5.4 Medium2023-11-15
CVE-2023-4689 Elementor Addon Elements <= 1.12.7 - Cross-Site Request Forgery — Addon Elements for Elementor (formerly Elementor Addon Elements) 5.4 Medium2023-11-15
CVE-2023-47550 WordPress Donations Made Easy – Smart Donations Plugin <= 4.0.12 is vulnerable to Cross Site Scripting (XSS) — Donations Made Easy – Smart Donations 7.1 High2023-11-14
CVE-2023-31230 WordPress Baidu Tongji generator Plugin <= 1.0.2 is vulnerable to Cross Site Request Forgery (CSRF) — Baidu Tongji generator 7.1 High2023-11-13
CVE-2023-32123 WordPress The7 Theme <= 11.7.3 is vulnerable to Cross Site Request Forgery (CSRF) — The7 6.1 Medium2023-11-13
CVE-2023-35877 WordPress Extra User Details Plugin <= 0.5 is vulnerable to Cross Site Request Forgery (CSRF) — Extra User Details 7.1 Medium2023-11-13
CVE-2023-39166 WordPress tagDiv Composer Plugin < 4.4 is vulnerable to Cross Site Request Forgery (CSRF) — tagDiv Composer 7.1 High2023-11-13
CVE-2023-40335 WordPress Cleverwise Daily Quotes Plugin <= 3.2 is vulnerable to Cross Site Scripting (XSS) — Cleverwise Daily Quotes 7.1 High2023-11-13
CVE-2023-46092 WordPress Webmaster Tools Plugin <= 2.0 is vulnerable to Cross Site Request Forgery (CSRF) — Webmaster Tools 7.1 Medium2023-11-13
CVE-2023-46201 WordPress Auto Login New User After Registration Plugin <= 1.9.6 is vulnerable to Cross Site Request Forgery (CSRF) — Auto Login New User After Registration 7.1 Medium2023-11-13
CVE-2023-46634 WordPress Custom My Account for Woocommerce Plugin <= 2.1 is vulnerable to Cross Site Request Forgery (CSRF) — Custom My Account for Woocommerce 7.1 High2023-11-13
CVE-2023-47516 WordPress Category Post List Widget Plugin <= 2.0 is vulnerable to Cross Site Scripting (XSS) — Category Post List Widget 7.1 High2023-11-13
CVE-2023-47652 WordPress Auto Affiliate Links Plugin <= 6.4.2.4 is vulnerable to Cross Site Request Forgery (CSRF) — Auto Affiliate Links 7.1 High2023-11-13
CVE-2023-35041 WordPress Webpushr Plugin <= 4.34.0 is vulnerable to Cross Site Request Forgery (CSRF) — Web Push Notifications – Webpushr 8.8 High2023-11-13
CVE-2023-32583 WordPress WP All Backup Plugin <= 2.4.3 is vulnerable to Cross Site Request Forgery (CSRF) — WP All Backup 6.3 Medium2023-11-13
CVE-2023-32588 WordPress Post State Tags Plugin <= 2.0.6 is vulnerable to Cross Site Request Forgery (CSRF) — Post State Tags 4.3 Medium2023-11-13
CVE-2023-33207 WordPress Stop Referrer Spam Plugin <= 1.3.0 is vulnerable to Cross Site Request Forgery (CSRF) — Stop Referrer Spam 4.3 Medium2023-11-13
CVE-2023-34378 WordPress WP Hide Post Plugin <= 2.0.10 is vulnerable to Cross Site Request Forgery (CSRF) — WP Hide Post 4.3 Medium2023-11-13
CVE-2023-34384 WordPress Kebo Twitter Feed Plugin <= 1.5.12 is vulnerable to Cross Site Request Forgery (CSRF) — Kebo Twitter Feed 5.4 Medium2023-11-13
CVE-2023-47669 WordPress Profile Builder Plugin <= 3.10.3 is vulnerable to Cross Site Request Forgery (CSRF) — User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor 5.4 Medium2023-11-13
CVE-2023-46618 WordPress Category SEO Meta Tags Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF) — Category SEO Meta Tags 4.3 Medium2023-11-13
CVE-2023-46619 WordPress Spider Facebook Plugin <= 1.0.15 is vulnerable to Cross Site Request Forgery (CSRF) — WDSocialWidgets 5.4 Medium2023-11-13
CVE-2023-46620 WordPress DeepL Pro API translation Plugin <= 2.3.9.1 is vulnerable to Cross Site Request Forgery (CSRF) — DeepL API translation plugin 4.3 Medium2023-11-13
CVE-2023-46625 WordPress Autolinks Manager Plugin <= 1.10.04 is vulnerable to Cross Site Request Forgery (CSRF) — Autolinks Manager 4.3 Medium2023-11-13

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