dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26059

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to 1.8.02.004 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Delta Electronics DIAEnergie (All versions prior to 1.8.02.004) has a blind SQL injection vulnerability that exists in GetQueryData. This allows an attacker to inject arbitrary SQL queries, retrieve and modify database contents, and execute system 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

Delta Electronics DIAEnergie contains a critical blind SQL injection vulnerability in the GetQueryData component affecting all versions prior to 1.8.02.004. The flaw allows unauthenticated attackers to inject arbitrary SQL queries, potentially leading to database exfiltration, modification, and OS command execution.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later to remediate the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the affected application and implement web application firewall rules to detect and block SQL injection attempts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiaenergieApplication
Affected:< 1.8.02.004

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 DIAEnergie installation and version
    Check Windows Programs and Features for 'DIAEnergie' entry, or access the application's About/Help section to view the installed version number
    Affected if The installed version is lower than 1.8.02.004
  2. Locate the web application endpoint
    Identify the base URL of the DIAEnergie web interface (typically hosted on IIS). The vulnerable component is the GetQueryData handler
    Affected if The web interface is exposed and accessible
  3. Verify the GetQueryData component exists
    Check for the presence of the GetQueryData handler in the application's web configuration or attempt to access a known endpoint pattern (such as /Handler/GetQueryData.ashx or similar)
    Affected if The GetQueryData handler is present and responds to requests
  4. Confirm database connectivity
    Verify that the DIAEnergie application connects to a SQL Server database. Check the application's configuration files for database connection strings
    Affected if The application uses a SQL Server database and the web interface can submit queries to it
  5. Assess network exposure
    Determine if the DIAEnergie web interface is accessible from untrusted networks. Check firewall rules and IIS bindings for the application
    Affected if The web interface is reachable from outside the local network without authentication restrictions

A user is affected if DIAEnergie version is below 1.8.02.004, the web interface is accessible, and the GetQueryData component handles unauthenticated SQL query submissions.

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
Upgrade available Upgrade to 1.8.02.004 or later
Fixed in 1.8.02.004
Interim mitigation

Upgrade DIAEnergie to version 1.8.02.004 or later to remediate the SQL injection vulnerability. If immediate patching is not possible, restrict network access to the affected application and implement web application firewall rules to detect and block SQL injection attempts.

Recommended fix High confidence

1.8.02.004

  1. Identify the current version of DIAEnergie installed in the environment
  2. Obtain and apply DIAEnergie version 1.8.02.004 or later from Delta Electronics
  3. After upgrading, verify that the GetQueryData endpoint no longer accepts arbitrary SQL injection payloads
  4. Confirm the application functions normally post-upgrade

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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