Is flarum/core vulnerable?

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

9advisories
2critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2021-32671XSS vulnerability with translatorcritical10.0>=1.0.0 and <1.0.21.0.2
CVE-2024-21641Flarum's logout Route allows open redirectsmedium6.5<1.8.51.8.5
CVE-2023-27577Path Traversal Vulnerability in `LESS` Parser allows reading of sensitive server filesmedium6.5<1.7.01.7.0
CVE-2022-41938Cross site scripting vulnerability with discussion titlescritical9.0>=1.5.0 and <1.6.21.6.2
CVE-2023-22489Any Flarum user including unactivated can reply in public discussions whose first post was permanently deletedlow3.5>=1.3.0 and <1.6.31.6.3
CVE-2023-40033Flarum vulnerable to LFI and Blind SSRF via Avatar uploadhigh7.1<1.8.01.8.0
CVE-2025-27794Flarum Vulnerable to Session Hijacking via Authoritative Subdomain Cookie Overwritemedium6.8<1.8.101.8.10
CVE-2026-41887Flarum: Path traversal in LESS parser via theme color settings (incomplete fix for CVE-2023-27577)medium4.9<1.8.16 or >=2.0.0-beta.1 and <2.0.0-rc.11.8.16, 2.0.0-rc.1
CVE-2023-22488Flarum notifications can leak restricted contentmedium6.8<1.6.31.6.3

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.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   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.