An issue was discovered in SmtpTransport in CakePHP 3.7.6. An unserialized object with modified internal properties can trigger arbitrary file overwriting upon destruction.
CakePHP is a development framework for PHP web apps. In affected versions the Cake\Database\Query::limit() and Cake\Database\Query::offset() methods are vulnerable to SQL injection if passed un-sanitized user request data. This issue has been fixed in 4.2.12, 4.3.11, 4.4.10. Users are advised to upgrade. Users unable to upgrade may mitigate this issue by using CakePHP's Pagination library. Manually validating or casting parameters to these methods will also mitigate the issue.
CakePHP 1.3.7 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by dispatcher.php and certain other files.
The validatePost function in libs/controller/components/security.php in CakePHP 1.3.x through 1.3.5 and 1.2.8 allows remote attackers to modify the internal Cake cache and execute arbitrary code via a crafted data[Token][fields] value that is processed by the unserialize function, as demonstrated by modifying the filemap cache to execute arbitrary local files.
A vulnerability exists in CakePHP versions 4.0.x through 4.1.3. The CsrfProtectionMiddleware component allows method override parameters to bypass CSRF checks by changing the HTTP request method to an arbitrary string that is not in the list of request methods that CakePHP checks. Additionally, the route middleware does not verify that this overriden method (which can be an arbitrary string) is actually an HTTP method.
The Xml class in CakePHP 2.1.x before 2.1.5 and 2.2.x before 2.2.1 allows remote attackers to read arbitrary files via XML data containing external entity references, aka an XML external entity (XXE) injection attack.
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass the CSRF protection mechanism via the method parameter.
CakePHP before 4.0.6 and 3.10.3 mishandles CSRF token generation. This might be remotely exploitable in conjunction with XSS.
End of life: 9/9/2026, End of support: 10/15/2023, Latest version: 4.4.18
End of life: 9/9/2026, End of support: 10/15/2023, Latest version: 4.4.18
End of life: 9/9/2026, End of support: 6/7/2022, Latest version: 4.3.11
End of life: 9/9/2026, End of support: 6/7/2022, Latest version: 4.3.11
End of life: 12/15/2022, End of support: 12/15/2021, Latest version: 3.10.5
End of life: 12/15/2022, End of support: 12/15/2021, Latest version: 3.10.5
End of life: 10/14/2023, End of support: 10/24/2021, Latest version: 4.2.12
End of life: 10/14/2023, End of support: 10/24/2021, Latest version: 4.2.12
End of support: 12/21/2020, Latest version: 4.1.7
End of support: 12/21/2020, Latest version: 4.1.7
End of support: 6/20/2021, Latest version: 3.9.10
End of support: 6/20/2021, Latest version: 3.9.10
End of support: 7/5/2020, Latest version: 4.0.10
End of support: 7/5/2020, Latest version: 4.0.10
End of support: 6/21/2020, Latest version: 3.8.13
End of support: 6/21/2020, Latest version: 3.8.13
End of support: 6/27/2019, Latest version: 3.7.9
End of support: 6/27/2019, Latest version: 3.7.9
End of support: 12/9/2018, Latest version: 3.6.15
End of support: 12/9/2018, Latest version: 3.6.15
End of support: 4/15/2018, Latest version: 3.5.18
End of support: 4/15/2018, Latest version: 3.5.18