Vulnerability Database · Packagist · Package report

flarum/core: vulnerability history, versions and safety

flarum/core is a package in the Packagist ecosystem. Vulert records 9 vulnerabilities for it across 59 releases, from Jun 2021 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded C2 H1 M5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 22 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on flarum/core i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 22 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 9 vulnerabilities on record across 4 years, 1 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 4 years · 1 in the last year i
  • Latest disclosure 22 Apr 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for flarum/core, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
v1.8.15 M1 Yes Details →
v1.8.14 M1 Yes Details →
v1.8.13 M1 Yes Details →
v1.8.12 M1 Yes Details →
v1.8.11 M1 Yes Details →
v1.8.10 M1 Yes Details →
v1.8.9 M2 Yes Details →
v1.8.8 M2 Yes Details →
v1.8.7 M2 Yes Details →
v1.8.6 M2 Yes Details →
v1.8.5 M2 Yes Details →
v1.8.4 M3 Yes Details →
v1.8.3 M3 Yes Details →
v1.8.2 M3 Yes Details →
v1.8.1 M3 Yes Details →
v1.8.0 M3 Yes Details →
v1.7.2 H1 M3 Yes Details →
v1.7.1 H1 M3 Yes Details →
v1.7.0 H1 M3 Yes Details →
v1.6.3 H1 M4 Yes Details →
v1.6.2 H1 M5 L1 Yes Details →
v1.6.1 C1 H1 M5 L1 Yes Details →
v1.6.0 C1 H1 M5 L1 Yes Details →
v1.5.0 C1 H1 M5 L1 Yes Details →
v1.4.1 H1 M5 L1 Yes Details →
v1.4.0 H1 M5 L1 Yes Details →
v1.3.1 H1 M5 L1 Yes Details →
v1.3.0 H1 M5 L1 Yes Details →
v1.2.1 H1 M5 Yes Details →
v1.2.0 H1 M5 Yes Details →
v1.1.1 H1 M5 Yes Details →
v1.1.0 H1 M5 Yes Details →
v1.0.4 H1 M5 Yes Details →
v1.0.3 H1 M5 Yes Details →
v1.0.2 H1 M5 Yes Details →
v1.0.1 C1 H1 M5 Yes Details →
v1.0.0 C1 H1 M5 Yes Details →
v0.1.0-beta.16 H1 M5 Yes Details →
v0.1.0-beta.15 H1 M5 Yes Details →
v0.1.0-beta.14.1 H1 M5 Yes Details →
v0.1.0-beta.14 H1 M5 Yes Details →
v0.1.0-beta.13 H1 M5 Yes Details →
v0.1.0-beta.12 H1 M5 Yes Details →
v0.1.0-beta.11.1 H1 M5 Yes Details →
v0.1.0-beta.11 H1 M5 Yes Details →
v0.1.0-beta.10 H1 M5 Yes Details →
v0.1.0-beta.9 H1 M5 Yes Details →
v0.1.0-beta.8.2 H1 M5 Yes Details →
v0.1.0-beta.8.1 H1 M5 Yes Details →
v0.1.0-beta.8 H1 M5 Yes Details →
v0.1.0-beta.7.2 H1 M5 Yes Details →
v0.1.0-beta.7.1 H1 M5 Yes Details →
v0.1.0-beta.7 H1 M5 Yes Details →
v0.1.0-beta.6 H1 M5 Yes Details →
v0.1.0-beta.5 H1 M5 Yes Details →
v0.1.0-beta.4 H1 M5 Yes Details →
v0.1.0-beta.3 H1 M5 Yes Details →
v0.1.0-beta.2 H1 M5 Yes Details →
v0.1.0-beta H1 M5 Yes Details →

Newest 59 of 59 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2023 4
  • 2024 1
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 9 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About flarum/core

Is flarum/core safe to use?

Vulert records 9 vulnerabilities for flarum/core in Packagist: 2 critical, 1 high, 5 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does flarum/core have?

9 vulnerabilities are recorded for flarum/core in the Packagist ecosystem: 2 critical, 1 high, 5 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new flarum/core vulnerabilities disclosed?

1 vulnerability was recorded for flarum/core in the last 12 months, and the oldest entry in this database dates to 07 Jun 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of flarum/core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor flarum/core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the flarum/core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.