Is flarum/nicknames 1.6 vulnerable?

Composer · 2 releases from 1.6.0 to 1.6.1 · latest flarum/nicknames is 2.0.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. flarum/nicknames 1.6.1, the last 1.6 release, is affected by 1 known security advisory (1 medium), including CVE-2026-30913. Upgrade to 1.8.3 or later to fix all of them.

Upgrade with:composer require flarum/nicknames:^1.8.3

Is your project on an affected flarum/nicknames?

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/nicknames 1.6.1

  • MediumCVE-2026-30913GHSA-3c4m-j3g4-hh2510 Mar 2026

    flarum/nicknames extension has display name injection in notification emails (autolink & markdown)

    Affected
    <1.8.3
    Fixed in
    1.8.3

Every flarum/nicknames 1.6.x release

Affected: 1.6.0 to 1.6.1. Latest flarum/nicknames: 2.0.1.

VersionKnown advisories
flarum/nicknames 1.6.1CVE-2026-30913
flarum/nicknames 1.6.0CVE-2026-30913

Which of your client projects are still on flarum/nicknames 1.6?

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

Other flarum/nicknames 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.