CVE-2026-31069 BillaBear is Vulnerable to SQL Injection in the EventRepository
An authenticated attacker can execute arbitrary SQL commands via unsanitized filter identifiers in BillaBear, potentially accessing or modifying data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-31069?
CVE-2026-31069 is a high-severity SQL injection vulnerability in n/a, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
BillaBear (all versions prior to Jan 2026) contains a SQL Injection vulnerability in the EventRepository. User-controlled input from metric filter names and aggregation properties is directly interpolated into SQL queries using sprintf() without proper sanitization or identifier quoting. Although filter values are parameterized, the filter identifiers (keys) are not. An authenticated attacker with ROLE_ACCOUNT_MANAGER permissions can exploit this to execute arbitrary SQL commands.
Weakness: CWE-89
Which versions are affected by CVE-2026-31069?
2 open source packages ship an affected version, including billabear/billabear.
| Package | Affected | Fixed in |
|---|---|---|
billabear/billabear Packagist | All versions to 2025.01.03 | None |
billabear/billabear Packagist | All versions to 2025.01.03 | None |
How do I fix CVE-2026-31069?
No fix has been published for CVE-2026-31069 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-31069 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31069 exists.
Sources
Also known as GHSA-xp6r-8pcc-xv5p.