dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26065

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 exists in GetLatestDemandNode. 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 (versions prior to 1.8.02.004) contains a blind SQL injection vulnerability in the GetLatestDemandNode function. This allows authenticated or unauthenticated attackers to inject arbitrary SQL queries, potentially leading to database exfiltration, modification, and OS command execution via database features.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later. As a temporary measure, implement network segmentation to restrict access to the affected interface and deploy WAF rules to detect SQL injection patterns.

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 installed version
    Locate the DIAEnergie installation directory and check version information in the application's about, help, or settings interface. Common locations include the program files directory for Deltaww software or the web application's login/page source for version details.
    Affected if The installed version is prior to 1.8.02.004 (for example, 1.7.x or 1.8.01.x)
  2. Confirm the web interface is accessible
    Attempt to access the DIAEnergie web portal URL (commonly on ports 80/443 or configured ports) from a browser to verify the application is running and reachable.
    Affected if The web interface is accessible over the network (this is required for the vulnerability to be exploitable)
  3. Determine if authentication is required for the vulnerable endpoint
    Review application documentation or test access to the GetLatestDemandNode function endpoint without valid credentials to confirm if the vulnerability is exploitable without authentication.
    Affected if The GetLatestDemandNode function can be reached without valid credentials or with default/weak credentials
  4. Assess network exposure of the affected interface
    Check firewall rules, network segments, and exposed IP addresses to determine if the DIAEnergie web interface is accessible from untrusted networks such as the internet or adjacent network segments.
    Affected if The interface is exposed to untrusted networks or the internet without proper access controls

A user is affected if they have DIAEnergie version prior to 1.8.02.004 installed AND the web interface is network-accessible, since the SQL injection in GetLatestDemandNode can then be exploited.

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. As a temporary measure, implement network segmentation to restrict access to the affected interface and deploy WAF rules to detect SQL injection patterns.

Recommended fix High confidence

1.8.02.004

  1. Upgrade DIAEnergie to version 1.8.02.004 or later
  2. After upgrading, verify that the GetLatestDemandNode component is no longer vulnerable to SQL injection
  3. Test that the application functions normally after the 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
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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