dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4317

CRITICAL · 9.3 CVSS v4.0 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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
SQL inyection (SQLi) vulnerability in Umami Software web application through an improperly sanitized parameter, which could allow an authenticated attacker to execute arbitrary SQL commands in the database.Specifically, they could manipulate the value of the 'timezone' request parameter by including malicious characters and SQL payload. The application would interpolate these values directly into the SQL query without first performing proper filtering or sanitization (e.g., using functions such as 'prisma.rawQuery', 'prisma.$queryRawUnsafe' or raw queries with 'ClickHouse'). The successful explotation of this vulnerability could allow an authenticated attacker to compromiso the data of the database and execute dangerous functions.

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 · moderate confidence

SQL injection vulnerability in Umami Software allows authenticated attackers to manipulate the 'timezone' request parameter with malicious SQL payloads. The application directly interpolates unsanitized input into SQL queries using Prisma raw query functions (prisma.$queryRawUnsafe, prisma.rawQuery) or ClickHouse raw queries, enabling arbitrary SQL command execution and full database compromise.

MitigationImplement proper input validation and parameterized queries for the 'timezone' parameter. Replace raw query functions with parameterized alternatives and perform input sanitization before database operations.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the installed Umami version
    Check package.json, version file, or run 'npm list umami' or 'yarn list umami' in the application directory to determine the exact version number
    Affected if The installed version is any version that processes the 'timezone' parameter through raw query functions without sanitization
  2. Locate timezone parameter handling code
    Search the codebase for API routes, controllers, or handlers that accept 'timezone' as a request parameter (query, body, or route param)
    Affected if The application accepts and processes a 'timezone' parameter from HTTP requests
  3. Inspect raw query usage with timezone input
    Search the codebase for prisma.$queryRawUnsafe, prisma.rawQuery, or ClickHouse raw query calls that incorporate the 'timezone' parameter directly into SQL strings
    Affected if Raw query functions concatenate or interpolate the timezone parameter without parameterized binding
  4. Verify input validation on timezone parameter
    Inspect middleware, validators, or sanitization logic that processes the timezone parameter before it reaches database queries
    Affected if No input validation, sanitization, or parameterized query binding exists for the timezone parameter
  5. Confirm authentication requirement
    Review whether the affected endpoint requires authentication (the CVE states authenticated attackers)
    Affected if The vulnerable timezone endpoint is accessible to authenticated users (any user with valid credentials)

The environment is affected if the installed Umami version processes the 'timezone' request parameter through Prisma or ClickHouse raw query functions without using parameterized queries or input sanitization.

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

Implement proper input validation and parameterized queries for the 'timezone' parameter. Replace raw query functions with parameterized alternatives and perform input sanitization before database operations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4317 — 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-4317 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