dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-31069

HIGH · 8.8 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in BillaBear's EventRepository where metric filter names and aggregation properties (filter keys/identifiers) are directly interpolated into SQL queries using sprintf() without proper sanitization or identifier quoting. While filter values are parameterized, the filter identifiers themselves are not, allowing authenticated attackers with ROLE_ACCOUNT_MANAGER permissions to inject arbitrary SQL commands.

MitigationReplace direct sprintf() interpolation with proper identifier quoting/escaping, or refactor to use a parameterized approach for column/table identifiers (e.g., allowlist of valid filter keys, or use a query builder that handles identifier binding safely).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify BillaBear installation
    Locate the BillaBear application installation directory. Look for composer.json or package.json files that identify the project as BillaBear, or check for the typical project structure with src/Repository/EventRepository.php
    Affected if The application is BillaBear and the installation directory is found
  2. Check BillaBear version
    Inspect the version file (such as version.txt, composer.json version field, or a config/version parameter) and determine if it predates January 2026. Compare against the affected version range (prior to Jan 2026)
    Affected if The installed version is prior to January 2026
  3. Locate vulnerable EventRepository code
    Search the codebase for src/Repository/EventRepository.php or similar EventRepository class. Inspect the file for sprintf() calls that interpolate filter key variables directly into SQL queries, particularly around metric filtering and aggregation logic
    Affected if EventRepository.php exists and contains unsanitized sprintf() interpolation of filter keys into SQL queries
  4. Verify metric/filter functionality is accessible
    Check if the application exposes any API endpoints or UI features that accept metric filter names and aggregation properties as user input. Look for routes related to events, metrics, analytics, or reporting that process filter parameters
    Affected if Metric filter or aggregation features are exposed and accept user-supplied filter key names
  5. Confirm ROLE_ACCOUNT_MANAGER access exists
    Review the application user roles and permissions system. Check if ROLE_ACCOUNT_MANAGER role is defined in the security configuration (such as security.yaml, roles.yaml, or the User entity). Identify any user accounts assigned this role
    Affected if ROLE_ACCOUNT_MANAGER role exists and is assignable to authenticated users, making the vulnerable functionality reachable

The environment is affected if BillaBear version prior to January 2026 is installed, the vulnerable sprintf() interpolation exists in EventRepository, and a user with ROLE_ACCOUNT_MANAGER can access the metric filter functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct sprintf() interpolation with proper identifier quoting/escaping, or refactor to use a parameterized approach for column/table identifiers (e.g., allowlist of valid filter keys, or use a query builder that handles identifier binding safely).

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31069 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data