flarum/sticky
[READ ONLY] Subtree split of Flarum sticky extension.
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 41
- Cadence
- ~2 months
- Last 12 months
- 14
Reach
- Stars
- 9
Details
- License
- MIT
- First release
- Nov 02, 2015
| Version | Released | |
|---|---|---|
v2.0.0-rc.8
pre
| ||
v2.0.0-rc.7
pre
| ||
v2.0.0-rc.6
pre
| ||
v1.8.3
patch
| ||
v2.0.0-rc.5
pre
| ||
v2.0.0-rc.4
pre
| ||
v2.0.0-rc.3
pre
| ||
v2.0.0-rc.2
pre
| ||
v2.0.0-rc.1
pre
| ||
v2.0.0-beta.8
pre
| ||
v2.0.0-beta.7
pre
| ||
v2.0.0-beta.6
pre
| ||
v2.0.0-beta.5
pre
| ||
v2.0.0-beta.4
pre
| ||
v2.0.0-beta.3
pre
| ||
v2.0.0-beta.2
pre
| ||
v2.0.0-beta.1
pre
| ||
v1.8.2
patch
| ||
v1.8.1
patch
| ||
v1.8.0
minor
| ||
v1.7.0
minor
| ||
v1.6.1
patch
| ||
v1.6.0
minor
| ||
v1.5.0
minor
| ||
v1.4.0
minor
| ||
v1.3.0
minor
| ||
v1.2.0
minor
| ||
v1.1.0
minor
| ||
v1.0.0
initial
| ||
v0.1.0-beta.16
pre
| ||
v0.1.0-beta.15.1
pre
| ||
v0.1.0-beta.15
pre
1 CVE
CVE-2021-21283
GHSA-h3gg-7wx2-cq3h
Jan 29, 2021
XSS in Flarum Sticky extension
Medium
ImpactA 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 Mithril's 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. PatchesThe 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. WorkaroundsForum administrators can disable the Sticky extension until they are able to apply the update. The vulnerability cannot be exploited while the extension is disabled. ReferencesFor more informationIf you have any questions or comments about this advisory, please start a new discussion on our support forum. If you discover a security vulnerability within Flarum, please send an e-mail to security@flarum.org. All security vulnerabilities will be promptly addressed. More details can be found in our security policy. Affected versions
v0.1.0-beta.14
v0.1.0-beta.15
Fixed in
0.1.0-beta.15.1
References
Updated Jul 08, 2026 · Source: OSV.dev | ||
v0.1.0-beta.14
pre
1 CVE
CVE-2021-21283
GHSA-h3gg-7wx2-cq3h
Jan 29, 2021
XSS in Flarum Sticky extension
Medium
ImpactA 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 Mithril's 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. PatchesThe 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. WorkaroundsForum administrators can disable the Sticky extension until they are able to apply the update. The vulnerability cannot be exploited while the extension is disabled. ReferencesFor more informationIf you have any questions or comments about this advisory, please start a new discussion on our support forum. If you discover a security vulnerability within Flarum, please send an e-mail to security@flarum.org. All security vulnerabilities will be promptly addressed. More details can be found in our security policy. Affected versions
v0.1.0-beta.14
v0.1.0-beta.15
Fixed in
0.1.0-beta.15.1
References
Updated Jul 08, 2026 · Source: OSV.dev |
v0.1.0-beta.14
pre
Dependencies (1)
Changelog
Compare changes
|
|
v0.1.0-beta.13
pre
| ||
v0.1.0-beta.12
pre
| ||
v0.1.0-beta.9
pre
| ||
v0.1.0-beta.8
pre
| ||
v0.1.0-beta.7
pre
| ||
v0.1.0-beta.6
pre
| ||
v0.1.0-beta.5
pre
| ||
v0.1.0-beta.3
pre
|