Skip to main content
VulnerabilityPublished Updated

CVE-2026-31069: BillaBear · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Until an official fix is available, restrict ROLE_ACCOUNT_MANAGER permissions to trusted users only and monitor for unusual database activity related to metric filter usage. Avoid exposing this functionality to untrusted users.

Description

BillaBear versions prior to January 2026 contain a SQL Injection vulnerability in the EventRepository component. This flaw arises because user-controlled input from metric filter names and aggregation properties is directly inserted into SQL queries without proper sanitization or quoting. An authenticated attacker with ROLE_ACCOUNT_MANAGER permissions can exploit this to execute arbitrary SQL commands. The vulnerability has a high severity score of 8.8 (CVSS 3.1) and affects confidentiality, integrity, and availability. No official patch or remediation guidance is currently available.

References

Community reviews

Loading reviews…