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

Goal: 1000 CNY · Raised: 1110 CNY

100%

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

4850 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-2021-32991 Delta Electronics DIAEnergie 跨站请求伪造漏洞 — Delta Electronics DIAEnergie 6.5 -2021-08-30
CVE-2021-24581 Blue Admin <= 21.06.01 - CSRF to Stored Cross-Site Scripting (XSS) — Blue Admin 8.2 -2021-08-30
CVE-2021-3730 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-08-23
CVE-2021-3729 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-08-23
CVE-2021-3728 Cross-Site Request Forgery (CSRF) in firefly-iii/firefly-iii — firefly-iii/firefly-iii 4.3 -2021-08-23
CVE-2021-34645 Shopping Cart & eCommerce Store <= 5.1.0 Cross-Site Request Forgery to Stored Cross-Site Scripting — Shopping Cart & eCommerce Store 8.8 High2021-08-19
CVE-2021-24380 Shantz WordPress QOTD <= 1.2.2 - Arbitrary Setting Update via CSRF — Shantz WordPress QOTD 4.3 -2021-08-16
CVE-2021-34661 WP Fusion Lite <= 3.37.18 Cross-Site Request Forgery to Data Deletion — WP Fusion Lite 6.1 Medium2021-08-09
CVE-2021-24467 Leaflet Map < 3.0.0 - Arbitrary Settings Update via CSRF Leading to Stored XSS — Leaflet Map 6.5 -2021-08-09
CVE-2021-34633 Youtube Feeder <= 2.0.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting — Youtube Feeder 8.8 High2021-08-05
CVE-2021-34634 Nifty Newsletters <= 4.0.23 - Cross-Site Request Forgery to Stored Cross-Site Scripting — Nifty Newsletters 8.8 High2021-08-05
CVE-2021-34631 NewsPlugin <= 1.0.18 - Cross-Site Request Forgery to Stored Cross-Site Scripting — NewsPlugin 8.8 High2021-08-05
CVE-2021-23849 Cross Site Request Forgery (CSRF) vulnerability in web based management interface — CPP Firmware 7.5 High2021-08-05
CVE-2021-34632 SEO Backlinks <= 4.0.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting — SEO Backlinks 8.8 High2021-08-02
CVE-2021-34628 Admin Custom Login <= 3.2.7 - Cross-Site Request Forgery to Stored Cross-Site Scripting — Admin Custom Login 8.8 High2021-08-02
CVE-2021-34637 Post Index <= 0.7.5 Cross-Site Request Forgery to Stored Cross-Site Scripting — Post Index 8.8 High2021-08-02
CVE-2021-32776 No CSRF form token cleanup on Windows servers — iTop 6.8 Medium2021-07-21
CVE-2021-21407 Portal : the CSRF token isn't validated — iTop 8.0 High2021-07-21
CVE-2021-34619 Cross-Site Request Forgery in WooCommerce Stock Manager WordPress Plugin — WooCommerce Stock Manager 8.8 High2021-07-21
CVE-2021-32774 Cross-Site Request Forgery (CSRF) in DataDump — DataDump 6.1 Medium2021-07-20
CVE-2021-34620 CSRF in WP Fluent Forms < 3.6.67 allows stored XSS and Privilege Escalation — WP Fluent Forms 8.8 -2021-07-07
CVE-2021-32730 No CSRF protection on the password change form — xwiki-platform 5.7 Medium2021-07-01
CVE-2021-32677 Cross-Site Request Forgery (CSRF) in FastAPI — fastapi 8.2 High2021-06-09
CVE-2020-10771 Red Hat Data Grid 跨站请求伪造漏洞 — Infinispan 8.3 -2021-06-02
CVE-2021-24328 WP Login Security and History <= 1.0 - CSRF to Stored Cross-Site Scripting (XSS) — WP Login Security and History 6.5 -2021-06-01
CVE-2021-24333 Content Copy Protection & Prevent Image Save <= 1.3 - CSRF to Stored Cross-Site Scripting (XSS) — Content Copy Protection & Prevent Image Save 7.1 -2021-06-01
CVE-2021-21549 Dell EMC XtremIO 跨站请求伪造漏洞 — XtremIO 8.8 High2021-05-21
CVE-2021-32632 CSRF allowing modification of commands, modules, banphrases through hidden iFrames — pajbot 2.4 Low2021-05-20
CVE-2021-24324 404 SEO Redirection <= 1.3 - CSRF to Stored Cross-Site Scripting (XSS) — 404 SEO Redirection 6.5 -2021-05-17
CVE-2021-24249 Business Directory Plugin < 5.11.2 - Arbitrary Listing Export — Business Directory Plugin – Easy Listing Directories for WordPress 6.5 -2021-05-05

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