dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-55082

HIGH · 8.7 CVSS v4.0 Published 2026-07-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 4 weeks old

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
DHIS2 is a flexible information system for data capture, management, validation, analytics and visualization. DHIS2 SQL View data endpoints allowed authenticated users with SQL View access to provide crafted filter values that were interpolated into generated SQL. An authenticated user with access to SQL View execution could manipulate SQL generated for SQL View filters and potentially access data outside the intended SQL View result set. This is distinct from CVE-2026-55084, which tracks the related SQL View filter column-name injection. Known affected release lines for this advisory: DHIS2 2.37, 2.38, and 2.39 before the 2026-06-09 EOS security updates. Patched by the 2026-06-09 EOS security updates for 2.37, 2.38, and 2.39. The same value-slot hardening was already present on later supported branches through DHIS2-20174 / PR #22253.

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

DHIS2 contains a SQL injection vulnerability in SQL View data endpoints where authenticated users with SQL View access can provide crafted filter values that get interpolated directly into generated SQL queries. This value-slot injection allows attackers to manipulate the SQL View filter logic and potentially access data outside the intended result set.

MitigationApply the 2026-06-09 EOS security updates for DHIS2 versions 2.37, 2.38, and 2.39, which implement value-slot hardening for SQL View filter parameters.

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:H/SC:N/SI:N/SA:N/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 DHIS2 version
    Access the DHIS2 administration interface and navigate to 'About' or 'System Info' in the system settings to view the installed version number. Alternatively, check the build metadata in the deployment artifacts or the version file in the DHIS2 home directory.
    Affected if The installed version is 2.37.x, 2.38.x, or 2.39.x (prior to the 2026-06-09 security patch)
  2. Confirm SQL View module is enabled
    Navigate to 'Apps' > 'App Management' in the DHIS2 administration interface and verify if the SQL View app is listed as installed and enabled, or query the system settings table for the SQL View configuration.
    Affected if SQL View app is installed and accessible to authenticated users
  3. Verify user SQL View permissions exist
    In the DHIS2 user management section, review user roles and authorities to identify any roles that include 'SQL_VIEW' or 'F_SQLVIEW_EXECUTE' authorities, or check the user_role_auths table for SQL View related permissions.
    Affected if Any authenticated users possess SQL View execution permissions
  4. Audit existing SQL Views for filter definitions
    Use the SQL View management interface or query the sqlview table in the DHIS2 database to list all SQL Views that contain filter parameters (check for 'filter=' or parameterized where clauses in the SQL definition).
    Affected if There are SQL Views with configurable filter parameters that could accept user input
  5. Check for anomalous SQL View query patterns
    Review DHIS2 application logs for SQL View execution endpoints (typically /api/sqlViews/{id}/data) and inspect the filter parameter values for unusual SQL syntax, quotes, or semicolons that may indicate injection attempts.
    Affected if Log analysis reveals SQL View filter parameters containing unexpected SQL fragments or injection signatures

A defender is affected if their DHIS2 instance runs version 2.37, 2.38, or 2.39 without the June 2026 security patch, has the SQL View module enabled, and allows authenticated users to create or access SQL Views with filter parameters.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply the 2026-06-09 EOS security updates for DHIS2 versions 2.37, 2.38, and 2.39, which implement value-slot hardening for SQL View filter parameters.

Recommended fix High confidence

DHIS2 2.37, 2.38, or 2.39 with 2026-06-09 EOS security updates applied

  1. 1. Identify the current DHIS2 version in use (2.37.x, 2.38.x, or 2.39.x)
  2. 2. Download the 2026-06-09 EOS security update for the respective version from the official DHIS2 repository
  3. 3. Back up the current DHIS2 database and configuration files
  4. 4. Stop the DHIS2 application service
  5. 5. Apply the security update following the standard DHIS2 upgrade procedure
  6. 6. Verify the update was applied correctly by checking the DHIS2 version information
  7. 7. Restart the DHIS2 application service
  8. 8. Test that SQL View functionality works correctly with the security fix in place
Caveat Standard DHIS2 upgrade precautions apply - test in non-production environment first, ensure database backup before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA5.0 h
26.0 hours of engineering $4,380
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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