concrete5/core vulnerabilities
Concrete core subtree split
- Registry
- Composer
- Latest
- 9.5.7
- License
- MIT
9 known advisories
The latest version, 9.5.7, is not affected by any of them. Projects on older versions may be.
composer require concrete5/core:^9.5.7Security advisories for concrete5/core
Path traversal in Concrete CMS
- Affected
- >=9.0.0 <9.1.0 · <8.5.8
- Fixed in
- 8.5.8, 9.1.0
Cross site scripting in Concrete CMS
- Affected
- >=9.0.0 <9.1.0 · <8.5.8
- Fixed in
- 8.5.8, 9.1.0
Code injection in concrete CMS
- Affected
- >=9.0.0 <9.1.0 · <8.5.8
- Fixed in
- 8.5.8, 9.1.0
Server-Side Request Forgery in Concrete CMS
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Server-Side Request Forgery in Concrete CMS
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Password exposure in concrete5/core
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Improper Privilege Management in Concrete CMS
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Exposure of sensitive information in concrete5/core
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Improper file handling in concrete5/core
- Affected
- <8.5.7
- Fixed in
- 8.5.7
Which of your client projects still run an old concrete5/core?
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.