Is flarum/mentions 1.3 vulnerable?

Composer · 2 releases from 1.3.0 to 1.3.1 · latest flarum/mentions is 2.0.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. flarum/mentions 1.3.1, the last 1.3 release, is affected by 1 known security advisory (1 high), including CVE-2023-22487. Upgrade to 1.6.3 or later to fix all of them.

Upgrade with:composer require flarum/mentions:^1.6.3

Is your project on an affected flarum/mentions?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting flarum/mentions 1.3.1

  • HighCVE-2023-22487GHSA-22m9-m3ww-53h310 Jan 2023

    Flarum post mentions can be used to read any post on the forum without access control

    Affected
    <1.6.3
    Fixed in
    1.6.3

Every flarum/mentions 1.3.x release

Affected: 1.3.0 to 1.3.1. Latest flarum/mentions: 2.0.3.

VersionKnown advisories
flarum/mentions 1.3.1CVE-2023-22487
flarum/mentions 1.3.0CVE-2023-22487

Which of your client projects are still on flarum/mentions 1.3?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact flarum/mentions version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other flarum/mentions versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.