Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-36676: n/a

0
High
VulnerabilityCVE-2024-36676cvecve-2024-36676
Published: Tue Jul 09 2024 (07/09/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2024-36676 is a high-severity vulnerability in BookStack versions before 24. 05. 1 caused by incorrect access control. It allows unauthenticated attackers to confirm the existence of system users and launch targeted denial-of-service attacks by abusing notification email functionality via public-facing forms. The vulnerability does not impact confidentiality or integrity but can severely affect availability by overwhelming notification systems. Exploitation requires no privileges or user interaction and can be performed remotely over the network. No known exploits are currently reported in the wild. Organizations using vulnerable BookStack instances should prioritize patching or apply mitigations to restrict access to public forms and monitor email notification systems. Countries with significant BookStack usage and reliance on open-source documentation platforms are at higher risk.

AI-Powered Analysis

AILast updated: 02/26/2026, 05:09:24 UTC

Technical Analysis

CVE-2024-36676 is an access control vulnerability identified in BookStack, an open-source platform for creating documentation and wikis. The flaw exists in versions prior to 24.05.1 and stems from improper validation of user access rights on public-facing forms. Specifically, attackers can leverage these forms to confirm whether specific user accounts exist within the system, effectively enumerating valid users. Beyond user enumeration, the vulnerability enables attackers to trigger targeted notification emails repeatedly, causing a denial-of-service (DoS) condition by overwhelming the email infrastructure or recipients. The CVSS 3.1 base score of 7.5 reflects a high severity due to the vulnerability's network attack vector, lack of required privileges or user interaction, and its impact on availability. The vulnerability is classified under CWE-79, which typically relates to improper neutralization of input leading to cross-site scripting, but here it is linked to access control issues. Although no public exploits have been reported, the ease of exploitation and potential for service disruption make this a significant threat for organizations relying on BookStack for internal or external documentation. The absence of patches at the time of reporting necessitates immediate attention to mitigate risk.

Potential Impact

The primary impact of CVE-2024-36676 is on the availability of services relying on BookStack's notification email system. Attackers can cause denial-of-service conditions by flooding notification channels, potentially disrupting communication workflows and administrative alerts. While confidentiality and integrity are not directly compromised, the ability to enumerate valid users can aid in further targeted attacks such as phishing or social engineering. Organizations with high dependency on BookStack for knowledge management may experience operational disruptions, loss of productivity, and increased support costs. Additionally, the public exposure of valid user accounts can weaken overall security posture by revealing internal user information. The vulnerability's network accessibility and lack of authentication requirements increase the risk of widespread exploitation, especially in environments where BookStack is exposed to the internet without adequate protections.

Mitigation Recommendations

To mitigate CVE-2024-36676, organizations should upgrade BookStack to version 24.05.1 or later as soon as patches become available. Until then, administrators should restrict access to public-facing forms by implementing network-level controls such as IP whitelisting or VPN access to limit exposure. Rate limiting or CAPTCHA mechanisms on notification forms can reduce the risk of automated abuse. Monitoring email server logs for unusual spikes in notification traffic can help detect exploitation attempts early. Additionally, reviewing and tightening user enumeration protections, such as generic error messages that do not reveal user existence, will reduce information leakage. Employing web application firewalls (WAFs) with custom rules to block suspicious requests targeting notification endpoints can provide an additional layer of defense. Regular security audits and user awareness training on phishing risks related to user enumeration should complement technical controls.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-05-30T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c63b7ef31ef0b5638f7

Added to database: 2/25/2026, 9:40:51 PM

Last enriched: 2/26/2026, 5:09:24 AM

Last updated: 2/26/2026, 9:34:54 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats