flarum/mentions
[READ ONLY] Subtree split of Flarum mentions extension.
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 50
- Cadence
- ~44 days
- Last 12 months
- 14
Reach
- Stars
- 18
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.6
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.5
patch
| ||
v1.8.4
patch
| ||
v1.8.3
patch
| ||
v1.8.2
patch
| ||
v1.8.1
patch
| ||
v1.8.0
minor
| ||
v1.7.0
minor
| ||
v1.6.3
patch
| ||
v1.6.1
patch
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.6.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.5.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.4.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.3.1
patch
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.3.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.2.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.1.3
patch
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.1.2
patch
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.1.1
patch
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.1.0
minor
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v1.0.0
initial
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.16
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.15
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.14
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev |
v0.1.0-beta.14
pre
Dependencies (1)
Changelog
Compare changes
|
|
v0.1.0-beta.13
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.12
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.10
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.9
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.8.1
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.8
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.7
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.6
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.5
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev | ||
v0.1.0-beta.3
pre
1 CVE
CVE-2023-22487
GHSA-22m9-m3ww-53h3
Jan 10, 2023
Flarum post mentions can be used to read any post on the forum without access control
7.7
/ 10
High
Network
Low
Low
None
Changed
High
None
None
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. ImpactThe attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown. All Flarum versions prior to PatchesThe vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using: You can then confirm you run the latest version using: WorkaroundsDisable the mentions extension. For more informationFor any questions or comments on this vulnerability please visit https://discuss.flarum.org/ For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly. Affected versions
v0.1.0-beta.10
v0.1.0-beta.12
v0.1.0-beta.13
v0.1.0-beta.14
v0.1.0-beta.15
v0.1.0-beta.16
v0.1.0-beta.3
v0.1.0-beta.5
v0.1.0-beta.6
v0.1.0-beta.7
v0.1.0-beta.8
v0.1.0-beta.8.1
+ 13 more Show less
v0.1.0-beta.9
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.2.0
v1.3.0
v1.3.1
v1.4.0
v1.5.0
v1.6.0
v1.6.1
Fixed in
1.6.3
References Updated Sep 10, 2026 · Source: OSV.dev |