CVE-2015-8379: CSRF

Published Jan 26, 2016
·
Updated

CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass the CSRF protection mechanism via the method parameter.

Affected Software

137 affected components
CakePHP CakePHP=2.0.0
CakePHP CakePHP=2.0.0-alpha
CakePHP CakePHP=2.0.0-beta
CakePHP CakePHP=2.0.0-dev
CakePHP CakePHP=2.0.0-rc1
CakePHP CakePHP=2.0.0-rc2
CakePHP CakePHP=2.0.0-rc3
CakePHP CakePHP=2.0.1
CakePHP CakePHP=2.0.2
CakePHP CakePHP=2.0.3
CakePHP CakePHP=2.0.4
CakePHP CakePHP=2.0.5
CakePHP CakePHP=2.0.6
CakePHP CakePHP=2.1.0
CakePHP CakePHP=2.1.0-alpha
CakePHP CakePHP=2.1.0-beta
CakePHP CakePHP=2.1.0-rc1
CakePHP CakePHP=2.1.1
CakePHP CakePHP=2.1.2
CakePHP CakePHP=2.1.3
CakePHP CakePHP=2.1.4
CakePHP CakePHP=2.1.5
CakePHP CakePHP=2.2.0
CakePHP CakePHP=2.2.0-beta
CakePHP CakePHP=2.2.0-rc1
CakePHP CakePHP=2.2.0-rc2
CakePHP CakePHP=2.2.1
CakePHP CakePHP=2.2.2
CakePHP CakePHP=2.2.3
CakePHP CakePHP=2.2.4
CakePHP CakePHP=2.2.5
CakePHP CakePHP=2.2.6
CakePHP CakePHP=2.2.7
CakePHP CakePHP=2.2.8
CakePHP CakePHP=2.2.9
CakePHP CakePHP=2.3.0
CakePHP CakePHP=2.3.0-beta
CakePHP CakePHP=2.3.0-rc1
CakePHP CakePHP=2.3.0-rc2
CakePHP CakePHP=2.3.1
CakePHP CakePHP=2.3.2
CakePHP CakePHP=2.3.3
CakePHP CakePHP=2.3.4
CakePHP CakePHP=2.3.5
CakePHP CakePHP=2.3.6
CakePHP CakePHP=2.3.7
CakePHP CakePHP=2.3.8
CakePHP CakePHP=2.3.9
CakePHP CakePHP=2.3.10
CakePHP CakePHP=2.4.0
CakePHP CakePHP=2.4.0-beta
CakePHP CakePHP=2.4.0-rc1
CakePHP CakePHP=2.4.0-rc2
CakePHP CakePHP=2.4.1
CakePHP CakePHP=2.4.2
CakePHP CakePHP=2.4.3
CakePHP CakePHP=2.4.4
CakePHP CakePHP=2.4.5
CakePHP CakePHP=2.4.6
CakePHP CakePHP=2.4.7
CakePHP CakePHP=2.4.8
CakePHP CakePHP=2.4.9
CakePHP CakePHP=2.4.10
CakePHP CakePHP=2.5.0
CakePHP CakePHP=2.5.0-beta
CakePHP CakePHP=2.5.0-rc1
CakePHP CakePHP=2.5.0-rc2
CakePHP CakePHP=2.5.1
CakePHP CakePHP=2.5.2
CakePHP CakePHP=2.5.3
CakePHP CakePHP=2.5.4
CakePHP CakePHP=2.5.5
CakePHP CakePHP=2.5.6
CakePHP CakePHP=2.5.7
CakePHP CakePHP=2.5.8
CakePHP CakePHP=2.5.9
CakePHP CakePHP=2.6.0
CakePHP CakePHP=2.6.0-beta
CakePHP CakePHP=2.6.0-rc1
CakePHP CakePHP=2.6.1
CakePHP CakePHP=2.6.2
CakePHP CakePHP=2.6.3
CakePHP CakePHP=2.6.4
CakePHP CakePHP=2.6.5
CakePHP CakePHP=2.6.6
CakePHP CakePHP=2.6.7
CakePHP CakePHP=2.6.8
CakePHP CakePHP=2.6.9
CakePHP CakePHP=2.6.10
CakePHP CakePHP=2.6.11
CakePHP CakePHP=2.6.12
CakePHP CakePHP=2.7.0
CakePHP CakePHP=2.7.0-rc1
CakePHP CakePHP=2.7.1
CakePHP CakePHP=2.7.2
CakePHP CakePHP=2.7.3
CakePHP CakePHP=2.7.4
CakePHP CakePHP=2.7.5
CakePHP CakePHP=2.7.6
CakePHP CakePHP=2.7.7
CakePHP CakePHP=2.7.8
CakePHP CakePHP=2.7.9
CakePHP CakePHP=2.8.0-rc1
CakePHP CakePHP=3.0.0
CakePHP CakePHP=3.0.0-alpha1
CakePHP CakePHP=3.0.0-alpha2
CakePHP CakePHP=3.0.0-beta1
CakePHP CakePHP=3.0.0-beta2
CakePHP CakePHP=3.0.0-beta3
CakePHP CakePHP=3.0.0-dev1
CakePHP CakePHP=3.0.0-dev2
CakePHP CakePHP=3.0.0-dev3
CakePHP CakePHP=3.0.0-rc1
CakePHP CakePHP=3.0.0-rc2
CakePHP CakePHP=3.0.1
CakePHP CakePHP=3.0.2
CakePHP CakePHP=3.0.3
CakePHP CakePHP=3.0.4
CakePHP CakePHP=3.0.5
CakePHP CakePHP=3.0.6
CakePHP CakePHP=3.0.7
CakePHP CakePHP=3.0.8
CakePHP CakePHP=3.0.9
CakePHP CakePHP=3.0.10
CakePHP CakePHP=3.0.11
CakePHP CakePHP=3.0.12
CakePHP CakePHP=3.0.13
CakePHP CakePHP=3.0.14
CakePHP CakePHP=3.0.15
CakePHP CakePHP=3.1.0
CakePHP CakePHP=3.1.0-beta1
CakePHP CakePHP=3.1.0-beta2
CakePHP CakePHP=3.1.0-rc1
CakePHP CakePHP=3.1.1
CakePHP CakePHP=3.1.2
CakePHP CakePHP=3.1.3
CakePHP CakePHP=3.1.4

Remediation

Patch Available

https://github.com/cakephp/cakephp/commit/0f818a23a876c01429196bf7623e1e94a50230f0

Event History

Jan 26, 2016
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2015-8379?

The severity level of CVE-2015-8379 is generally considered important due to its ability to bypass CSRF protections.

2

How do I fix CVE-2015-8379?

To fix CVE-2015-8379, update CakePHP to version 3.1.5 or later.

3

What versions are affected by CVE-2015-8379?

CVE-2015-8379 affects CakePHP 2.x and 3.x versions prior to 3.1.5.

4

Can CVE-2015-8379 be exploited remotely?

Yes, CVE-2015-8379 can be exploited remotely by attackers to bypass CSRF protections.

5

What measures should be taken if I can't immediately update for CVE-2015-8379?

If an immediate update is not possible, implement additional server-side validations to mitigate the risk of CSRF attacks.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203