Read the docs
TI-2021-04383 Aliases CVE-2021-21283GHSA-h3gg-7wx2-cq3h

XSS in Flarum Sticky extension.

Priority LOW 26CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Required
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-79.

Summary

Flarum is an open source discussion platform for websites. The "Flarum Sticky" extension versions 0.1.0-beta.14 and 0.1.0-beta.15 has a cross-site scripting vulnerability. A change in release beta 14 of the Sticky extension caused the plain text content of the first post of a pinned discussion to be injected as HTML on the discussion list. The issue was discovered following an internal audit. Any HTML would be injected through the m.trust() helper. This resulted in an HTML injection where <script> tags would not be executed. However it was possible to run javascript from other HTML attributes, enabling a cross-site scripting (XSS) attack to be performed. Since the exploit only happens with the first post of a pinned discussion, an attacker would need the ability to pin their own discussion, or be able to edit a discussion that was previously pinned. On forums where all pinned posts are authored by your staff, you can be relatively certain the vulnerability has not been exploited. Forums where some user-created discussions were pinned can look at the first post edit date to find whether the vulnerability might have been exploited. Because Flarum doesn't store the post content history, you cannot be certain if a malicious edit was reverted. The fix will be available in version v0.1.0-beta.16 with Flarum beta 16. The fix has already been back-ported to Flarum beta 15 as version v0.1.0-beta.15.1 of the Sticky extension. Forum administrators can disable the Sticky extension until they are able to apply the update. The vulnerability cannot be exploited while the extension is disabled.

Why it matters now

EPSS 0.00797 56th percentileScored 2026-11-07
Fix Fixed flarum/sticky (Packagist): 0.1.0-beta.15.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
flarumsticky>=v0.1.0-beta.14 <=v0.1.0-beta.15—No fix listedCNA
—flarum/sticky (Packagist)0.1.0-beta.14 to before 0.1.0-beta.15.10.1.0-beta.15.1Patch availableGHSA-h3gg-7wx2-cq3h
  • sticky Vendorflarum Affected >=v0.1.0-beta.14 <=v0.1.0-beta.15 Fixed in — No fix listed CNA
  • flarum/sticky (Packagist) Vendor— Affected 0.1.0-beta.14 to before 0.1.0-beta.15.1 Fixed in 0.1.0-beta.15.1 Patch available GHSA-h3gg-7wx2-cq3h

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:flarum:sticky:0.1.0:beta14:*:*:*:*:*:*0.1.0 beta14Vulnerableflarum
cpe:2.3:a:flarum:sticky:0.1.0:beta15:*:*:*:*:*:*0.1.0 beta15Vulnerableflarum
  • cpe:2.3:a:flarum:sticky:0.1.0:beta14:*:*:*:*:*:* Versions 0.1.0 beta14 Vulnerable ·flarum
  • cpe:2.3:a:flarum:sticky:0.1.0:beta15:*:*:*:*:*:* Versions 0.1.0 beta15 Vulnerable ·flarum

Remediation

  • Fix · GHSA-h3gg-7wx2-cq3h flarum/sticky (Packagist) Fixed in 0.1.0-beta.15.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2021-21283
  2. 2026-10-03 Alias added: GHSA-h3gg-7wx2-cq3h

References

Sources