symfony/framework-bundle vulnerabilities
Provides a tight integration between Symfony components and the Symfony full-stack framework
- Registry
- Composer
- Latest
- 8.1.9
- License
- MIT
3 known advisories
The latest version, 8.1.9, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require symfony/framework-bundle:^8.1.9Security advisories for symfony/framework-bundle
Code injection in the way Symfony implements translation caching in FrameworkBundle
- Affected
- >=2.0.0 <2.3.18 · >=2.4.0 <2.4.8 · >=2.5.0 <2.5.2
- Fixed in
- 2.3.18, 2.4.8, 2.5.2
CSRF token missing in Symfony
- Affected
- >=5.3.14 <5.3.15 · >=5.4.3 <5.4.4 · >=6.0.3 <6.0.4
- Fixed in
- 5.3.15, 5.4.4, 6.0.4
Symfony Cross-site Scripting (XSS) vulnerability
- Affected
- >=2.7.0 <2.7.51 · >=2.8.0 <2.8.50 · >=3.0.0 <3.4.26 · >=4.0.0 <4.1.12 · >=4.2.0 <4.2.7
- Fixed in
- 2.7.51, 2.8.50, 3.4.26, 4.1.12, 4.2.7
Which of your client projects still run an old symfony/framework-bundle?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.