CVE-2026-24742: Discourse staff action logs expose sensitive information to moderators
Discourse is an open source discussion platform. In versions prior to 3.5.4, 2025.11.2, 2025.12.1, and 2026.1.0, non-admin moderators can view sensitive information in staff action logs that should be restricted to administrators only. The exposed information includes webhook payload URLs and secrets, API key details, site setting changes, private message content, restricted category names and structures, and private chat channel titles. This allows moderators to bypass intended access controls and extract confidential data by monitoring the staff action logs. With leaked webhook secrets, an attacker could potentially spoof webhook events to integrated services. This issue is patched in versions 3.5.4, 2025.11.2, 2025.12.1, and 2026.1.0. As a workaround, site administrators should review and limit moderator appointments to fully trusted users. There is no configuration-based workaround to prevent this access.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-24742?
CVE-2026-24742 is classified as a high severity vulnerability due to the exposure of sensitive information to non-admin moderators.
How do I fix CVE-2026-24742?
To fix CVE-2026-24742, upgrade Discourse to version 3.5.4 or later, or to 2025.11.2 or later.
What is the impact of CVE-2026-24742?
CVE-2026-24742 allows non-admin moderators to view sensitive staff action logs, potentially compromising user privacy and security.
Which versions of Discourse are affected by CVE-2026-24742?
Discourse versions prior to 3.5.4, 2025.11.2, 2025.12.1, and 2026.1.0 are affected by CVE-2026-24742.
Who is affected by CVE-2026-24742?
Non-admin moderators using affected versions of Discourse are at risk due to their ability to access restricted sensitive information.