Is lavalite/cms vulnerable?

Composer lavalite/cms has 14 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

14advisories
1critical
0on CISA KEV
12no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-42188Lavalite vulnerable to Arbitrary File Read via Directory Traversalhigh7.5=9.0.0–
CVE-2023-27238LavaLite vulnerable to web cache poisoningcritical9.8<=9.0.0–
CVE-2017-1000467Stored XSS in LavaLite 5.2.4medium5.4<=5.2.4–
CVE-2018-16551Stored XSS in LavaLite 5.5medium5.4all versions–
CVE-2020-23234Cross Site Scripting in LavaLite CMSmedium4.8<=5.8.0–
CVE-2023-27237LavaLite CMS vulnerable to host header injection attackmedium6.1<=9.0.0–
CVE-2020-23700Cross-site scripting in LavaLite-CMSmedium4.8<=5.8.0–
CVE-2020-36397LavaLite Stored Cross-site Scripting vulnerabilitymedium5.4<=5.8.0–
CVE-2020-28124Cross Site Scripting (XSS) in LavaLite 5.8.0medium5.4<7.0.17.0.1
CVE-2020-36395Stored XSS in LavaLite 5.8.0medium5.4<5.8.05.8.0
CVE-2024-31828Lavalite CMS Cross Site Scripting vulnerabilitymedium6.1=10.1.0–
CVE-2020-36396Stored XSS in LavaLite 5.8.0medium5.4<=5.8.0–
CVE-2023-30124LavaLite vulnerable to Cross Site Scriptingmedium5.4<=9.0.0–
CVE-2025-71177LavaLite CMS affected by a stored cross-site scripting vulnerabilitymedium0.0<=10.1.0–

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.