CVE-2026-31069
SQL Injection in BillaBear Prior to Jan 2026
Publication date: 2026-05-19
Last updated on: 2026-05-20
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| billabear | billabear | to 2026-01-01 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-31069 is a SQL Injection vulnerability found in BillaBear versions prior to January 2026. The issue exists in the EventRepository component where user-controlled input from metric filter names and aggregation properties is directly inserted into SQL queries using sprintf() without proper sanitization or quoting of identifiers.
While the filter values themselves are parameterized, the filter identifiers (keys) are not, which allows an authenticated attacker with ROLE_ACCOUNT_MANAGER permissions to exploit this flaw and execute arbitrary SQL commands on the database.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with certain authenticated permissions to execute arbitrary SQL commands on the backend database. This can lead to unauthorized data access, data modification, or deletion.
Such exploitation could compromise the integrity and confidentiality of your data, potentially leading to data breaches, loss of sensitive information, or disruption of service.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is caused by improper sanitization of user-controlled input in SQL queries within BillaBear versions prior to January 2026. Immediate mitigation steps include:
- Restrict access to users with ROLE_ACCOUNT_MANAGER permissions to trusted personnel only.
- Apply any available patches or updates from BillaBear that address this SQL Injection vulnerability.
- Review and sanitize all user inputs, especially metric filter names and aggregation properties, to prevent direct interpolation into SQL queries.
- Implement proper parameterization and identifier quoting in SQL queries to avoid injection.
- Monitor logs for suspicious SQL activity or unauthorized access attempts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is a SQL Injection in BillaBear that allows an authenticated attacker with specific permissions to execute arbitrary SQL commands. Such vulnerabilities can lead to unauthorized access or manipulation of sensitive data.
While the provided context does not explicitly mention compliance impacts, SQL Injection vulnerabilities generally pose risks to data confidentiality and integrity, which are critical concerns under standards like GDPR and HIPAA.
Exploitation of this vulnerability could potentially result in data breaches or unauthorized data exposure, thereby affecting compliance with regulations that mandate protection of personal and health information.