flarum/core vulnerabilities
Delightfully simple forum software.
- Registry
- Composer
- Latest
- 2.0.2
- License
- MIT
9 known advisories
The latest version, 2.0.2, is not affected by any of them. Projects on older versions may be.
composer require flarum/core:^2.0.2Is your project on an affected flarum/core?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for flarum/core
Flarum: Path traversal in LESS parser via theme color settings (incomplete fix for CVE-2023-27577)
- Affected
- <1.8.16 · >=2.0.0-beta.1 <2.0.0-rc.1
- Fixed in
- 1.8.16, 2.0.0-rc.1
Flarum Vulnerable to Session Hijacking via Authoritative Subdomain Cookie Overwrite
- Affected
- <1.8.10
- Fixed in
- 1.8.10
Flarum's logout Route allows open redirects
- Affected
- <1.8.5
- Fixed in
- 1.8.5
Flarum vulnerable to LFI and Blind SSRF via Avatar upload
- Affected
- <1.8.0
- Fixed in
- 1.8.0
Path Traversal Vulnerability in `LESS` Parser allows reading of sensitive server files
- Affected
- <1.7.0
- Fixed in
- 1.7.0
Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted
- Affected
- >=1.3.0 <1.6.3
- Fixed in
- 1.6.3
Flarum notifications can leak restricted content
- Affected
- <1.6.3
- Fixed in
- 1.6.3
Cross site scripting vulnerability with discussion titles
- Affected
- >=1.5.0 <1.6.2
- Fixed in
- 1.6.2
XSS vulnerability with translator
- Affected
- >=1.0.0 <1.0.2
- Fixed in
- 1.0.2
Is your flarum/core version vulnerable?
Which of your client projects still run an old flarum/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.