Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain presenter role in any meeting
-
DeliveryDiscover or enumerate presentationId from target meeting
-
ExploitCraft GraphQL delete mutation with foreign presentationId
-
ExecutionSubmit to /api/graphql without meeting-scoping check
-
PersistServer deletes victim meeting's presentation
-
ImpactTarget meeting disrupted
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | The attacker must hold an active presenter role in any BigBlueButton meeting on the target server - moderator or viewer roles alone are insufficient. The attacker must also know the presentationId (a server-assigned identifier) of a presentation belonging to a different concurrent meeting; this ID is not advertised publicly and requires either participation in the victim meeting, access to server logs, or enumeration via other means. The AC:H CVSS metric reflects this prerequisite. Exploitation is constrained to BigBlueButton instances running versions prior to 3.0.29. There are no additional configuration requirements - any default deployment of the affected version is susceptible once a presenter session is established and a foreign presentationId is known. The impact is limited to integrity and availability of the victim meeting's presentation content; no confidentiality loss or code execution is possible through this path. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L) scores 4.9 (Medium), which accurately reflects the real-world risk profile. AC:H captures the prerequisite that the attacker must obtain a presentationId from a different meeting - this ID is not publicly broadcast, so some reconnaissance or insider knowledge is required. PR:L correctly reflects that a presenter role is the minimum authentication threshold; anonymous users cannot exploit this. The Scope:Changed metric is appropriate because the impact falls outside the attacker's own meeting boundary, disrupting a separate victim meeting. No EPSS score was provided in the input, and no CISA KEV listing exists, consistent with the attack complexity and limited blast radius. The practical priority for most deployments is moderate: the vulnerability enables availability disruption and limited integrity loss rather than data exfiltration or code execution, and exploitation is gated on knowing a foreign presentationId. There is no indication of active or widespread exploitation. However, for multi-tenant hosted BigBlueButton environments serving many concurrent meetings, the cross-tenant sabotage potential elevates real-world concern beyond what the raw numerical score suggests. |
| Exploit ScenarioDerived | A malicious presenter authenticated to Meeting A issues a crafted GraphQL mutation to /api/graphql supplying the presentationId of a document uploaded in Meeting B, which they obtained by attending or monitoring Meeting B's session. Because the server previously validated only the existence of the presentationId and not its meeting ownership, the presentation is permanently deleted from Meeting B, disrupting that meeting's participants without any visible alert to Meeting B's organizer. No public proof-of-concept code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Cross-meeting presentation deletion in BigBlueButton prior to 3.0.29 allows an authenticated presenter in one meeting to permanently delete presentations belonging to a different concurrent meeting by supplying an arbitrary presentationId through the /api/graphql endpoint. The affected Scala handler RemovePresentationPubMsgHdlr issued database deletes scoped only by presentationId, with no verification that the target presentation belonged to the caller's meeting. No public exploit or CISA KEV listing has been identified at time of analysis, but exploitation requires only a valid presenter session and knowledge of a foreign presentationId, making it a realistic cross-tenant sabotage vector in multi-meeting deployments.
RemediationAI
Upgrade BigBlueButton to version 3.0.29 or later, which contains the confirmed fix per the vendor GitHub release at https://github.com/bigbluebutton/bigbluebutton/releases/tag/v3.0.29 and the patching commit c9e93f9af07b9661e286d101b83cbccb891c551f. The fix is a server-side change to the Scala data access layer; no client-side update is required. If an immediate upgrade is not feasible, a practical interim control is to restrict who can be assigned the presenter role - since only presenters can trigger the vulnerable code path, limiting presenter assignment to trusted internal users reduces the exploitable attack surface. Restricting network access to the /api/graphql endpoint to authenticated sessions only does not mitigate this issue, as the flaw requires only a valid presenter session. There are no known non-upgrade workarounds that fully eliminate the authorization bypass.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BigBlueButton's backend is built on an Akka actor system (akka-bbb-apps) that processes meeting events in Scala. The vulnerable handler, RemovePresentationPubMsgHdlr.scala, received a client-supplied presentationId from the GraphQL API and called PresPresentationDAO.delete(presentationId) with a filter on presentationId alone, making the deletion scoped globally across the database rather than within the caller's meeting. This is a textbook CWE-639 (Authorization Bypass Through User-Controlled Key) flaw: user-supplied key is trusted without validating ownership. The fix in commit c9e93f9a adds meetingId to the delete query - the caller's liveMeeting.props.meetingProp.intId is retrieved server-side and ANDed with the presentationId filter, preventing cross-meeting lookup. CPE cpe:2.3:a:bigbluebutton:bigbluebutton:*:*:*:*:*:*:*:* covers all releases prior to 3.0.29.
Know when Bigbluebutton gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L
AC:H because exploitation requires out-of-band knowledge of a foreign presentationId; PR:L because presenter authentication is mandatory; S:C because impact crosses meeting boundaries.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
BigBlueButton is an open-source virtual classroom. Prior to 3.0.29, BigBlueButton presenters could submit a presentationId through /api/graphql that identified a presentation belonging to another meeting. akka-bbb-apps/src/main/scala/org/bigbluebutton/core/apps/presentationpod/RemovePresentationPubMsgHdlr.scala did not verify the presentation's meeting identifier before deletion, allowing a presenter who knew the identifier to delete another meeting's presentation and disrupt its availability. This issue is fixed in version 3.0.29.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Bigbluebutton
View allBigBlueButton through 2.2.28 uses Ghostscript for processing of uploaded EPS documents, and consequently may be subject
BigBlueButton before 2.2.6 allows remote attackers to read arbitrary files because the presfilename (lowercase) value ca
BigBlueButton Greenlight before 2.5.6 allows HTTP header (Host and Origin) attacks, which can result in Account Takeover
The installation procedure in BigBlueButton before 2.2.28 (or earlier) uses ClueCon as the FreeSWITCH password, which al
Denial of service in BigBlueButton versions prior to 3.0.13 lets an authenticated meeting participant freeze or crash a
Chat denial of service in BigBlueButton before 3.0.13 lets an authenticated meeting participant crash chat for every att
An issue was discovered in BigBlueButton through 2.2.29. Rated high severity (CVSS 7.5), this vulnerability is remotely
The installation procedure in BigBlueButton before 2.2.28 (or earlier) exposes certain network services to external inte
BigBlueButton before 2.2.27 has an unsafe JODConverter setting in which LibreOffice document conversions can access exte
BigBlueButton before 2.2.5 allows remote attackers to obtain sensitive files via Local File Inclusion. Rated high severi
BigBlueButton versions 3.0.21 and below allow remote denial of service when ClamAV is configured following official docu
In BigBlueButton before 2.2.28 (or earlier), the client-side Mute button only signifies that the server should stop acce
EUVD-2026-63683
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB