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-46780 WordPress Alter Plugin <= 1.0 is vulnerable to Cross Site Request Forgery (CSRF) — Alter 4.3 Medium2023-11-06
CVE-2023-46779 WordPress EasyRecipe Plugin <= 3.5.3251 is vulnerable to Cross Site Request Forgery (CSRF) — EasyRecipe 5.4 Medium2023-11-06
CVE-2023-46778 WordPress Auto Limit Posts Reloaded Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF) — Auto Limit Posts Reloaded 4.3 Medium2023-11-06
CVE-2023-46777 WordPress Feather Login Page Plugin <= 1.1.3 is vulnerable to Cross Site Request Forgery (CSRF) — Custom Login Page | Temporary Users | Rebrand Login | Login Captcha 5.4 Medium2023-11-06
CVE-2023-46776 WordPress Auto Excerpt everywhere Plugin <= 1.5 is vulnerable to Cross Site Request Forgery (CSRF) — Auto Excerpt everywhere 4.3 Medium2023-11-06
CVE-2023-46775 WordPress Original texts Yandex WebMaster Plugin <= 1.18 is vulnerable to Cross Site Request Forgery (CSRF) — Original texts Yandex WebMaster 4.3 Medium2023-11-06
CVE-2023-47182 WordPress Login Screen Manager Plugin <= 3.5.2 is vulnerable to Cross Site Scripting (XSS) — Login Screen Manager 7.1 High2023-11-06
CVE-2023-42027 IBM CICS TX cross-site request forgery — CICS TX Standard 4.3 Medium2023-11-02
CVE-2023-5900 Cross-Site Request Forgery in pkp/pkp-lib — pkp/pkp-lib 3.5 Low2023-11-01
CVE-2023-5898 Cross-Site Request Forgery (CSRF) in pkp/pkp-lib — pkp/pkp-lib 8.1 -2023-11-01
CVE-2023-5897 Cross-Site Request Forgery (CSRF) in pkp/customLocale — pkp/customLocale 8.1 -2023-11-01
CVE-2023-5902 Cross-Site Request Forgery (CSRF) in pkp/pkp-lib — pkp/pkp-lib 8.1 -2023-11-01
CVE-2023-5899 Cross-Site Request Forgery (CSRF) in pkp/pkp-lib — pkp/pkp-lib 8.1 -2023-11-01
CVE-2023-5893 Cross-Site Request Forgery (CSRF) in pkp/pkp-lib — pkp/pkp-lib 8.1 -2023-11-01
CVE-2023-45670 Frigate cross-site request forgery in `config_save` and `config_set` request handlers — frigate 7.5 High2023-10-30
CVE-2023-43649 baserCMS CSRF vulnerability in Content preview Feature — basercms 4.7 Medium2023-10-30
CVE-2023-45317 Sielco Radio Link and Analog FM Transmitters Cross-Site Request Forgery — Analog FM transmitter 8.8 High2023-10-26
CVE-2023-5802 WordPress WP Knowledgebase Plugin <= 1.3.4 is vulnerable to Cross Site Request Forgery (CSRF) — WordPress Knowledge base & Documentation Plugin – WP Knowledgebase 4.3 Medium2023-10-26
CVE-2023-46204 WordPress Duplicate Theme Plugin <= 0.1.6 is vulnerable to Cross Site Request Forgery (CSRF) — Duplicate Theme 4.3 Medium2023-10-24
CVE-2023-46202 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 4.3 Medium2023-10-24
CVE-2023-46198 WordPress Appointment Calendar Plugin <= 2.9.6 is vulnerable to Cross Site Request Forgery (CSRF) — Appointment Calendar 5.4 Medium2023-10-24
CVE-2023-46193 WordPress Internal Link Building Plugin <= 1.2.3 is vulnerable to Cross Site Request Forgery (CSRF) — Internal Link Building 4.3 Medium2023-10-24
CVE-2023-46191 WordPress Open Graph Metabox Plugin <= 1.4.4 is vulnerable to Cross Site Request Forgery (CSRF) — Open Graph Metabox 4.3 Medium2023-10-24
CVE-2023-46190 WordPress Novo-Map : your WP posts on custom google maps Plugin <= 1.1.2 is vulnerable to Cross Site Request Forgery (CSRF) — Novo-Map : your WP posts on custom google maps 4.3 Medium2023-10-24
CVE-2023-46189 WordPress Google Calendar Events Plugin <= 3.2.5 is vulnerable to Cross Site Request Forgery (CSRF) — Simple Calendar – Google Calendar Plugin 4.3 Medium2023-10-24
CVE-2023-46152 WordPress WOLF Plugin <= 1.0.7.1 is vulnerable to Cross Site Request Forgery (CSRF) — WOLF – WordPress Posts Bulk Editor and Manager Professional 4.3 Medium2023-10-24
CVE-2023-46151 WordPress Product Category Tree Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF) — Product Category Tree 4.3 Medium2023-10-24
CVE-2023-46150 WordPress WP Radio plugin <= 3.1.9 is vulnerable to Cross Site Request Forgery (CSRF) — WP Radio 5.4 Medium2023-10-24
CVE-2023-46095 WordPress Smooth Scroll Links Plugin <= 1.1.0 is vulnerable to Cross Site Request Forgery (CSRF) — Smooth Scroll Links [SSL] 5.4 Medium2023-10-22
CVE-2023-46089 WordPress Userback Plugin <= 1.0.13 is vulnerable to Cross Site Request Forgery (CSRF) — Userback 4.3 Medium2023-10-22

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