/

CVE-2026-46682

Severity:

HIGH RISK

(8.5)

SQL Injection (CWE-89) in BigBlueButton Breakout Rooms

CVE-2026-46682

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL execution and application database compromise

Severity:

HIGH RISK

(8.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

BigBlueButton contained a SQL injection vulnerability in breakout-room visibility queries because authenticated moderator-supplied meeting and user identifiers were inserted into SQL statements without safe parameterization. An authenticated moderator could exploit this behavior to influence database queries, potentially exposing, modifying, or disrupting application data.

Affected context

The vulnerability occurs in BigBlueButton deployments that use affected pre-3.0.23 application code and process breakout-room visibility requests through refreshBreakoutRoomsVisibleForUsers. The risk exists when meeting and user identifier values can reach database queries through the moderator-facing application path without being separated from SQL syntax by parameterized query handling.

Exploit preconditions

  • Attack surface: BigBlueButton breakout-room visibility functionality
  • Required access: An authenticated account with moderator privileges
  • Trigger point: Processing of meetingId and userId values by refreshBreakoutRoomsVisibleForUsers
  • Why exploitation is possible: User-controlled values are interpolated into SQL queries rather than safely bound as data

Why this happens

The underlying bug is SQL injection, mapped to CWE-89. The application constructs database queries by combining SQL syntax with externally influenced identifier values, allowing input to alter the intended meaning of the statement. This insecure pattern occurs when query parameters are treated as trusted query fragments instead of being passed through parameterized database interfaces.

Potential impact

  • An attacker may read data accessible to the application database account.
  • An attacker could modify or delete application records.
  • Database integrity and breakout-room state may be disrupted.
  • Sensitive information may be disclosed to an authorized but malicious moderator.
  • Further compromise could occur if the database account has excessive privileges or dangerous database features enabled.

General mitigation guidance

Mitigation generally focuses on removing SQL construction from untrusted input and reducing the authority of the database connection.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for every externally influenced value.
  • Applying allowlist-based validation for identifiers while treating validation as an additional control rather than a substitute for parameterization.
  • Separating query construction from data binding and avoiding string interpolation in database statements.
  • Limiting database-account privileges to the minimum operations required by the application.
  • Restricting database network exposure and using separate accounts or schemas where practical.
  • Preserving authorization checks so moderator access does not imply broader database access.

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules that identify string interpolation, concatenation, or formatting within SQL statements.
  • Code review checks for database calls that accept constructed query strings instead of bound parameters.
  • Runtime monitoring for unusual query errors, unexpected database statements, and anomalous access to records outside normal meeting scope.
  • Policy enforcement requiring parameterized queries through approved database-access libraries.
  • Automated security testing that supplies unexpected identifier values to authenticated application endpoints in controlled environments.

Sources

SourceLink
github.comgithub.com/bigbluebutton/bigbluebutton/commit/3365e340e0c102de0f8ea007c05053b562b6fa2b
github.comgithub.com/bigbluebutton/bigbluebutton/releases/tag/v3.0.23
github.comgithub.com/bigbluebutton/bigbluebutton/security/advisories/GHSA-gfv2-46v4-jvw5

Frequently asked

questions

It can be exploitable through the BigBlueButton application interface when the vulnerable breakout-room functionality is reachable by an authenticated moderator. It does not generally require direct network access to the database.

The described attack requires authenticated moderator-level access or another ability to submit values to the affected request path.

The safest pattern is to use prepared statements or parameterized queries for all meeting and user identifiers, combined with strict authorization and input validation.

Enforce parameterized-query policies, review database access code for interpolation or concatenation, use least-privileged database accounts, and include authenticated SQL injection testing in security validation.

Find out what's already
exploitable in your codebase.