Flarum is a forum software for building communities. Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@#p` syntax. 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 `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions. 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. The 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 1.6.3 are affected. The vulnerability has been fixed and published as flarum/core v1.6.3. As a workaround, user can disable the mentions extension.
Priority: --
CVSS v3: 4.3
Component:
Publish Date: Jan 11, 2023
Related ID: --
CVSS v2: MEDIUM
Modified Date: Jan 12, 2023
Find out more about CVE-2023-22487 from the MITRE-CVE dictionary and NIST NVD
Login may be required to access defects or downloads.
| Product Name |
Status |
Defect |
Fixed |
Downloads |
| Linux |
| Wind River Linux LTS 17 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux 8 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux 9 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux 7 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux LTS 21 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux LTS 22 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux LTS 18 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux LTS 19 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux CD release |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux 6 |
Not Vulnerable |
-- |
-- |
-- |
| Wind River Linux LTS 23 |
Not Vulnerable |
-- |
-- |
-- |
| VxWorks |
| VxWorks 7 |
Not Vulnerable |
-- |
-- |
-- |
| VxWorks 6.9 |
Not Vulnerable |
-- |
-- |
-- |
| Helix Virtualization Platform Cert Edition |
| Helix Virtualization Platform Cert Edition |
Not Vulnerable |
-- |
-- |
-- |
| Product Name |
Status |
Defect |
Fixed |
Downloads |
Notes
Requires LTSS - customers must have active LTSS (Long Term Security Shield) Support to receive up-to-date information about vulnerabilities that may affect legacy software. Please contact your Wind River account team or see https://docs.windriver.com/bundle/Support_and_Maintenance_Supplemental_Terms_and_Conditions and https://support2.windriver.com/index.php?page=plc for more information.
