phpwarden
FeaturesComparePricingAdvisoriesBlogDocsChangelogLog in
Log inStart free

Is concrete5/core vulnerable?

Composer concrete5/core has 9 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

9advisories
1critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2021-22968Improper file handling in concrete5/corehigh7.2<8.5.78.5.7
CVE-2022-30117Path traversal in Concrete CMScritical9.1>=9.0.0 and <9.1.0 or <8.5.89.1.0, 8.5.8
CVE-2022-21829Code injection in concrete CMShigh8.0>=9.0.0 and <9.1.0 or <8.5.89.1.0, 8.5.8
CVE-2021-22970Server-Side Request Forgery in Concrete CMSmedium0.0<8.5.78.5.7
CVE-2021-22967Exposure of sensitive information in concrete5/coremedium0.0<8.5.78.5.7
CVE-2021-22951Password exposure in concrete5/coremedium0.0<8.5.78.5.7
CVE-2022-30120Cross site scripting in Concrete CMSlow3.1>=9.0.0 and <9.1.0 or <8.5.89.1.0, 8.5.8
CVE-2021-22966Improper Privilege Management in Concrete CMShigh8.8<8.5.78.5.7
CVE-2021-22969Server-Side Request Forgery in Concrete CMSmedium0.0<8.5.78.5.7

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.