All reports
Medium

Symfony CSRF Vulnerability

Affected versions

Version ranges need review.

Affected versions
>= 3.3.0, < 3.3.13
Fixed version
3.3.13
Affected versions
>=2.7.0,<2.7.38|>=2.8.0,<2.8.31|>=3.0.0,<3.1.0|>=3.1.0,<3.2.0|>=3.2.0,<3.2.14|>=3.3.0,<3.3.13
Fixed version
Not reported
Affected versions
>= 2.7.0, < 2.7.38
Fixed version
2.7.38
Affected versions
>= 3.0.0, < 3.2.14
Fixed version
3.2.14
Affected versions
>= 2.8.0, < 2.8.31
Fixed version
2.8.31
Affected versions
>= 3.3.0, < 3.3.13
Fixed version
3.3.13
Affected versions
>=2.7.0,<2.7.38|>=2.8.0,<2.8.31|>=3.0.0,<3.1.0|>=3.1.0,<3.2.0|>=3.2.0,<3.2.14|>=3.3.0,<3.3.13
Fixed version
Not reported
Affected versions
>= 2.7.0, < 2.7.38
Fixed version
2.7.38
Affected versions
>= 3.0.0, < 3.2.14
Fixed version
3.2.14
Affected versions
>= 2.8.0, < 2.8.31
Fixed version
2.8.31
Affected versions
>= 3.3.0, < 3.3.13
Fixed version
3.3.13
Affected versions
>= 3.0.0, < 3.2.14
Fixed version
3.2.14
Affected versions
>= 2.7.0, < 2.7.38
Fixed version
2.7.38
Affected versions
>= 2.8.0, < 2.8.31
Fixed version
2.8.31
Affected versions
>=2.7.0,<2.7.38|>=2.8.0,<2.8.31|>=3.0.0,<3.1.0|>=3.1.0,<3.2.0|>=3.2.0,<3.2.14|>=3.3.0,<3.3.13
Fixed version
Not reported

Exploitation

CVE-2017-16653

Probability of exploitation in the next 30 days: 1.49%

FIRST EPSS · 2026-11-21

Description

An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.

Links