CakePHP <= 3.2.0 "_method" CSRF Protection Bypass Vulnerability

Credit: Egidio Romano
Risk: Low
Local: No
Remote: Yes
CWE: CWE-352

CVSS Base Score: 6.8/10
Impact Subscore: 6.4/10
Exploitability Subscore: 8.6/10
Exploit range: Remote
Attack complexity: Medium
Authentication: No required
Confidentiality impact: Partial
Integrity impact: Partial
Availability impact: Partial

--------------------------------------------------------------- CakePHP <= 3.2.0 "_method" CSRF Protection Bypass Vulnerability --------------------------------------------------------------- [-] Software Link: [-] Affected Versions: Version 3.2.0 RC1 and prior 3.x versions. Version 2.8.0 RC1 and prior 2.x versions. [-] Vulnerability Description: CakePHP provides some built-in security features including CSRF and Form Tampering protection. Under certain circumstances it might be possible to bypass such security checks, since they are performed only when the HTTP request is e.g. POST or PUT. CakePHP?s Router class uses a number of different indicators to detect the HTTP method being used, like the "_method" POST parameter and the "X_HTTP_METHOD_OVERRIDE" and "REQUEST_METHOD" headers. By abusing this behavior an attacker might be able to carry out CSRF attacks against CakePHP applications which do not check the HTTP method being used before executing side-effects. This is possible by overriding the HTTP method with a web page like this: <html> <body> <form action="http://[HOST]/user/add" method="POST"> <input name="_method" type="hidden" value="CSRF" /> <input name="user" type="hidden" value="hacker" /> <input name="password" type="hidden" value="pwd" /> </form> <script>document.forms[0].submit()</script> </body> </html> [-] Solution: No official solution is currently available. The vendor updated the official documentation stating that developers should always check the HTTP method before executing side-effects. NOTE: version 3.1.5 includes a bugfix for this issue stating "CSRF validation is applied to all HTTP methods that are not ?GET?, ?OPTIONS? or ?HEAD?. This prevents invalid HTTP methods from bypassing CSRF validation.", however this is a partial fix which does not solve the vulnerability, because the bypass might still work by using one of the unprotected HTTP methods. [-] Disclosure Timeline: [10/11/2015] - Vendor notified [26/11/2015] - Vendor tried to mitigate the issue with the following commit: [01/12/2015] - Vendor response stating this issue has been addressed in version 3.1.5 and the documentation has been updated [01/12/2015] - CVE number requested [01/12/2015] - CVE number assigned [12/01/2016] - Public disclosure [-] CVE Reference: The Common Vulnerabilities and Exposures project ( has assigned the name CVE-2015-8379 to this vulnerability. [-] Credits: Vulnerability discovered by Egidio Romano of Minded Security. [-] Original Advisory: [-] Other References:


Vote for this issue:


Thanks for you vote!


Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2019,


Back to Top