CVE-2023-22489

Flarum is a discussion platform for websites. If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status. This includes users that don't have a validated email. Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies. Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion. This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to. In combination with the email notification settings, this could also be used as a way to send unsolicited emails. Versions between `v1.3.0` and `v1.6.3` are impacted. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.

• CWE-862

• https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015Patch, Third Party Advisory
• https://github.com/flarum/framework/releases/tag/v1.6.3Release Notes, Third Party Advisory
• https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725Mitigation, Third Party Advisory
• https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015Patch, Third Party Advisory
• https://github.com/flarum/framework/releases/tag/v1.6.3Release Notes, Third Party Advisory
• https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725Mitigation, Third Party Advisory

Published

Jan 13, 2023

Last Modified

Jun 17, 2026

Status

Modified

• Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-22483cmark-gfm is GitHub's fork of cmark, a CommonMark parsing an…7.5
• CVE-2023-22484cmark-gfm is GitHub's fork of cmark, a CommonMark parsing an…7.5
• CVE-2023-22485cmark-gfm is GitHub's fork of cmark, a CommonMark parsing an…5.3
• CVE-2023-22486cmark-gfm is GitHub's fork of cmark, a CommonMark parsing an…7.5
• CVE-2023-22487Flarum is a forum software for building communities. Using t…4.3
• CVE-2023-22488Flarum is a forum software for building communities. Using t…5.4
• CVE-2023-2249The wpForo Forum plugin for WordPress is vulnerable to Local…8.8
• CVE-2023-22490Git is a revision control system. Using a specially-crafted …5.5
• CVE-2023-22491Gatsby is a free and open source framework based on React th…5.4
• CVE-2023-22492ZITADEL is a combination of Auth0 and Keycloak. RefreshToken…5.9
• CVE-2023-22493RSSHub is an open source RSS feed generator. RSSHub is vulne…7.5
• CVE-2023-22494Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…