# 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.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-xp6r-8pcc-xv5p

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-31069?

2 open source packages ship an affected version, including billabear/billabear.


| Package | Ecosystem | 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.

## Is CVE-2026-31069 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31069 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31069 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31069 exists.

Affected packages and fixed versions:
- billabear/billabear (Packagist): affected all versions up to 2025.01.03; no fix listed
- billabear/billabear (Packagist): affected all versions up to 2025.01.03; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31069/ (Markdown: https://insights.sbomify.com/CVE-2026-31069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31069
- OSV: https://osv.dev/vulnerability/CVE-2026-31069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31069/
Summaries are generated and may contain mistakes; the official description above is the record.