CVE-2026-30913: Flarum/nicknames Flarum/nicknames Extension Has Display Name Vulnerability

MODERATE
Advisory Identifier: GHSA-3c4m-j3g4-hh25
CVSS 4.6
CWE-79
Published
Advisory Summary

CVE-2026-30913 is a MODERATE (CVSS 4.6) flarum/nicknames extension has display name vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Flarum/nicknames libraries in the Packagist ecosystem. The issue involves flarum/nicknames extension has display name injection in notification emails (autolink & markdown). Remediation is available by upgrading affected packages to version 1.8.3.

CVE-2026-30913 at a Glance

CVE Identifier CVE-2026-30913
GHSA Identifier GHSA-3c4m-j3g4-hh25
Severity MODERATE
CVSS v3.1 Base Score 4.6
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Flarum/nicknames
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-30913

To remediate this vulnerability, upgrade all affected Flarum/nicknames dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flarum/nicknames fixed: 1.8.3
Upgrade flarum/nicknames to 1.8.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for flarum/nicknames

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-30913, inspect your project dependencies for Flarum/nicknames:

inspect dependencies for flarum/nicknames

Analyze the terminal output to locate any version of Flarum/nicknames in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Flarum/nicknames, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary When the `flarum/nicknames` extension is enabled, a registered user can set their nickname to a string that email clients interpret as a hyperlink. The nickname is inserted verbatim into plain-text notification emails, and recipients may be misled into visiting attacker-controlled domains. ## Affected package - **`flarum/nicknames`** — permissive display name driver that allows special characters; affected since initial release on the `1.x` branch Any third-party display name driver that permits special characters would be equally affected. ## Variants 1. **Domain autolink** — a nickname such as `nasty.com` is automatically converted to a clickable hyperlink by virtually all email clients (Gmail, Outlook, Apple Mail, Thunderbird). 2. **Markdown link syntax** — a nickname such as `[CLICK](https://evil.com)` is rendered as a clickable hyperlink by email clients that auto-render markdown in plain-text emails (e.g. Apple Mail, Thunderbird). ## Steps to reproduce **Variant 1 (autolink — affects all email clients)** 1. Enable `flarum/nicknames`, set nickname to `nasty.com` 2. Trigger a notification email to another user (e.g. follow them, mention them) 3. The nickname appears as a clickable link in the received email **Variant 2 (markdown — affects markdown-rendering email clients)** 1. Enable `flarum/nicknames`, set nickname to `[CLICK](https://evil.com)` 2. Trigger a notification email to another user 3. In a markdown-rendering email client (e.g. Apple Mail), the nickname appears as a clickable link ## Impact Phishing / social engineering: victims may be misled into visiting attacker-controlled URLs via links appearing to originate from a trusted platform notification email. Variant 1 is exploitable against virtually all email clients without any special conditions. - CVSS v3.1: `AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N` — **4.6 Medium** ## Root cause The default username-based display name driver constrains values to `[a-zA-Z0-9_-]+`, making it immune. `flarum/nicknames` introduced permissive validation (min/max length and an optional admin-configured regex) that allows arbitrary characters including those meaningful in URL and markdown contexts. This has been the case since the first commit of the extension. ## Proposed fix - Add validation in `flarum/nicknames` to reject or sanitize nicknames containing characters that email clients may interpret as URLs or markdown links - Alternatively, sanitize the display name before insertion into notification email bodies so that legitimate nicknames like `Jane.Smith` are preserved but rendered safely ## References - Bug bounty submission: SBB-L4ZVAFH8 (Intigriti)

CVE-2026-30913 Affected Flarum/nicknames Versions

1 component(s)
Fixed Versions:
1.8.3
Product / Package Ecosystem Affected Versions Fixed Version
flarum/nicknames
Packagist
< 1.8.3
1.8.3

References

Frequently Asked Questions

What is CVE-2026-30913?
CVE-2026-30913 is a security vulnerability in Flarum/nicknames involving flarum/nicknames extension has display name injection in notification emails (autolink & markdown) under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Flarum/nicknames versions are affected?
Affected versions include releases prior to 1.8.3 across affected packages: flarum/nicknames.
What version fixes CVE-2026-30913?
Upgrading to 1.8.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flarum/nicknames affected?
Yes, flarum/nicknames is affected in releases prior to 1.8.3. Upgrade your dependency to 1.8.3 or later.
What is the CVSS score of CVE-2026-30913?
CVE-2026-30913 has a CVSS v3.1 base score of 4.6 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-30913?
CVE-2026-30913 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for CVE-2026-30913?
Run the dependency tree command: 'inspect dependencies for flarum/nicknames'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3c4m-j3g4-hh25",
  "modified" : "2026-03-10T18:44:19Z",
  "published" : "2026-03-10T00:56:30Z",
  "aliases" : [ "CVE-2026-30913" ],
  "summary" : "flarum/nicknames extension has display name injection in notification emails (autolink & markdown)",
  "details" : "## Summary\n\nWhen the `flarum/nicknames` extension is enabled, a registered user can set their nickname to a string that email clients interpret as a hyperlink. The nickname is inserted verbatim into plain-text notification emails, and recipients may be misled into visiting attacker-controlled domains.\n\n## Affected package\n\n- **`flarum/nicknames`** — permissive display name driver that allows special characters; affected since initial release on the `1.x` branch\n\nAny third-party display name driver that permits special characters would be equally affected.\n\n## Variants\n\n1. **Domain autolink** — a nickname such as `nasty.com` is automatically converted to a clickable hyperlink by virtually all email clients (Gmail, Outlook, Apple Mail, Thunderbird).\n2. **Markdown link syntax** — a nickname such as `[CLICK](https://evil.com)` is rendered as a clickable hyperlink by email clients that auto-render markdown in plain-text emails (e.g. Apple Mail, Thunderbird).\n\n## Steps to reproduce\n\n**Variant 1 (autolink — affects all email clients)**\n1. Enable `flarum/nicknames`, set nickname to `nasty.com`\n2. Trigger a notification email to another user (e.g. follow them, mention them)\n3. The nickname appears as a clickable link in the received email\n\n**Variant 2 (markdown — affects markdown-rendering email clients)**\n1. Enable `flarum/nicknames`, set nickname to `[CLICK](https://evil.com)`\n2. Trigger a notification email to another user\n3. In a markdown-rendering email client (e.g. Apple Mail), the nickname appears as a clickable link\n\n## Impact\n\nPhishing / social engineering: victims may be misled into visiting attacker-controlled URLs via links appearing to originate from a trusted platform notification email. Variant 1 is exploitable against virtually all email clients without any special conditions.\n\n- CVSS v3.1: `AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N` — **4.6 Medium**\n\n## Root cause\n\nThe default username-based display name driver constrains values to `[a-zA-Z0-9_-]+`, making it immune. `flarum/nicknames` introduced permissive validation (min/max length and an optional admin-configured regex) that allows arbitrary characters including those meaningful in URL and markdown contexts. This has been the case since the first commit of the extension.\n\n## Proposed fix\n\n- Add validation in `flarum/nicknames` to reject or sanitize nicknames containing characters that email clients may interpret as URLs or markdown links\n- Alternatively, sanitize the display name before insertion into notification email bodies so that legitimate nicknames like `Jane.Smith` are preserved but rendered safely\n\n## References\n\n- Bug bounty submission: SBB-L4ZVAFH8 (Intigriti)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "flarum/nicknames"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/flarum/framework/security/advisories/GHSA-3c4m-j3g4-hh25"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30913"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/flarum/nicknames/commit/4dde99729abdce8f6e2a7437c86e38735fdcca28"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/flarum/framework"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/flarum/nicknames/releases/tag/v1.8."
  }, {
    "type" : "WEB",
    "url" : "https://github.com/flarum/nicknames/releases/tag/v1.8.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-10T00:56:30Z",
    "nvd_published_at" : "2026-03-10T17:40:15Z"
  }
}