dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26667

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

A blind SQL injection vulnerability exists in the GetDemandAnalysisData component of Delta Electronics DIAEnergie (all versions prior to 1.8.02.004), allowing unauthenticated attackers to inject arbitrary SQL queries, read or modify database contents, and potentially execute system commands.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later. If immediate upgrade is not feasible, implement a web application firewall (WAF) with SQL injection rules and restrict network access to the affected system.

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. Confirm DIAEnergie installation
    Check if Delta Electronics DIAEnergie is installed on the system by looking in Windows Programs and Features or checking for the installation directory (commonly in C:\Program Files\Delta Electronics\DIAEnergie or similar)
    Affected if DIAEnergie is found installed on the system
  2. Determine installed DIAEnergie version
    Locate the version information in the application files, typically found in an About page within the web interface, or check assembly/version files in the installation directory. Compare the version number against 1.8.02.004
    Affected if The installed version is lower than 1.8.02.004 (e.g., 1.7.x, 1.8.0.x, 1.8.01.x)
  3. Verify GetDemandAnalysisData component is accessible
    Check if the web application exposes the GetDemandAnalysisData endpoint. This is typically accessible via HTTP/HTTPS at a path containing 'GetDemandAnalysisData' or similar. Attempt to access this endpoint or review web server logs for requests to this component
    Affected if The GetDemandAnalysisData component is exposed and responds to requests without authentication
  4. Confirm no compensating controls are in place
    Review whether a WAF (Web Application Firewall) with SQL injection protection is deployed in front of the DIAEnergie application, or if network access is restricted to authorized users only
    Affected if No WAF with SQL injection rules is present AND the system is directly accessible from the network without authentication restrictions

A user is affected if DIAEnergie is installed with a version lower than 1.8.02.004 AND the GetDemandAnalysisData component is accessible without authentication and without a WAF or network restriction blocking SQL injection attempts.

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. If immediate upgrade is not feasible, implement a web application firewall (WAF) with SQL injection rules and restrict network access to the affected system.

Recommended fix High confidence

1.8.02.004

  1. Contact Delta Electronics to obtain the DIAEnergie version 1.8.02.004 or later patch/update
  2. Apply the update in accordance with vendor documentation
  3. Verify the update was successfully applied by checking the DIAEnergie version
  4. Test that the GetDemandAnalysisData function operates correctly after the update

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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