Is flarum/nicknames 1.8 vulnerable?

Composer · 4 releases from 1.8.0 to 1.8.3 · latest flarum/nicknames is 2.0.1 · checked 18 Nov 2026

No known advisories in the last release

flarum/nicknames 1.8.3, the last 1.8 release, has no known advisories. 1 advisory affects earlier 1.8.x releases, so update to 1.8.3.

Update within 1.8: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

Fixed within 1.8.x, affecting earlier releases

  • 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.8.x release

Affected: 1.8.0 to 1.8.2. 1.8.3 is not affected. Latest flarum/nicknames: 2.0.1.

VersionKnown advisories
flarum/nicknames 1.8.3None
flarum/nicknames 1.8.2CVE-2026-30913
flarum/nicknames 1.8.1CVE-2026-30913
flarum/nicknames 1.8.0CVE-2026-30913

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

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.