This SQL injection in BigBlueButton's BreakoutRoomUserDAO is notable less for its technical mechanism than for what its existence reveals about the codebase's security posture. The vulnerability requires authenticated moderator access, which isn't a mitigation — it's a diagnostic. In virtual classroom software, moderators are the primary users (teachers, facilitators), not peripheral administrators. This means the 'authenticated prerequisite' doesn't narrow the blast radius so much as it describes the intended user base having direct database access to their own platform's data. The trust boundary wasn't misconfigured; it was never drawn at all. Moderator accounts in BBB accumulate privilege incrementally through feature requests evaluated against 'does this let the moderator do their job' rather than 'does this expand the attack surface.' The fix in a single DAO file patches the symptom without resetting that underlying assumption. The more important question is temporal: when was BreakoutRoomUserDAO introduced relative to BigBlueButton's adoption of Slick's lifted embeddings? If this predates the migration to injection-safe defaults, it represents legacy persistence code that survived an architectural transition as invisible sediment — a pattern other legacy DAOs likely share. The remediation debt here exceeds the vulnerability debt. Check other DAO files written before or during the Slick migration for raw string interpolation; the probability that this pattern exists elsewhere in unreviewed legacy persistence code is high, and a single CVE fix creates dangerous normalization that the threat model hasn't changed.
CVE-2026-46682
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBigBlueButton is an open-source virtual classroom. Prior to 3.0.23, BigBlueButton allowed authenticated moderators to inject SQL through the meetingId and userId values used by refreshBreakoutRoomsVisibleForUsers in akka-bbb-apps/src/main/scala/org/bigbluebutton/core/db/BreakoutRoomUserDAO.scala. The method interpolated those values into breakout room visibility queries, allowing arbitrary SQL execution against the application database. This issue is fixed in version 3.0.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUser input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.
General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.23
- Upgrade BigBlueButton to version 3.0.23 or later to address the SQL injection vulnerability in the refreshBreakoutRoomsVisibleForUsers method in akka-bbb-apps/src/main/scala/org/bigbluebutton/core/db/BreakoutRoomUserDAO.scala
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis SQL injection in BigBlueButton's BreakoutRoomUserDAO is notable less for its technical mechanism than for what its existence reveals about the codebase's security posture. The vulnerability requires authenticated moderator access, which isn't a mitigation — it's a diagnostic. In virtual classroom software, moderators are the primary users (teachers, facilitators), not peripheral administrators. This means the 'authenticated prerequisite' doesn't narrow the blast radius so much as it describes the intended user base having direct database access to their own platform's data. The trust boundary wasn't misconfigured; it was never drawn at all. Moderator accounts in BBB accumulate privilege incrementally through feature requests evaluated against 'does this let the moderator do their job' rather than 'does this expand the attack surface.' The fix in a single DAO file patches the symptom without resetting that underlying assumption. The more important question is temporal: when was BreakoutRoomUserDAO introduced relative to BigBlueButton's adoption of Slick's lifted embeddings? If this predates the migration to injection-safe defaults, it represents legacy persistence code that survived an architectural transition as invisible sediment — a pattern other legacy DAOs likely share. The remediation debt here exceeds the vulnerability debt. Check other DAO files written before or during the Slick migration for raw string interpolation; the probability that this pattern exists elsewhere in unreviewed legacy persistence code is high, and a single CVE fix creates dangerous normalization that the threat model hasn't changed.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46682 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data