dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26069

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 HandlerPage_KID.ashx. 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 contain a blind SQL injection vulnerability in the HandlerPage_KID.ashx web handler. Attackers can inject arbitrary SQL queries through unsanitized input, potentially allowing database content retrieval/modification and OS command execution via database interactions.

MitigationUpgrade to DIAEnergie version 1.8.02.004 or later. If immediate patching is not feasible, implement input validation and parameterized queries in the affected handler, and restrict network access to the vulnerable endpoint.

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 version
    Locate the DIAEnergie installation directory and check for version information in file metadata, installer logs, or the application itself. Common locations include the installation folder and the application's about or help section.
    Affected if Installed version is lower than 1.8.02.004
  2. Verify HandlerPage_KID.ashx exists
    Search for the file HandlerPage_KID.ashx in the web application's handlers or scripts directory. This is typically found in the web root or bin folder of the DIAEnergie web interface.
    Affected if The file exists in the web application directory
  3. Confirm web interface is network accessible
    Check network configuration and firewall rules to determine if the DIAEnergie web interface (port 80/443 or configured web port) is reachable from untrusted networks.
    Affected if The web interface is exposed to untrusted or public networks
  4. Inspect HandlerPage_KID.ashx for lack of parameterized queries
    If code access is available, review the HandlerPage_KID.ashx source code to verify whether SQL queries are constructed using string concatenation instead of parameterized queries or prepared statements.
    Affected if SQL queries in the handler use string concatenation with user input rather than parameterized queries

You are affected if DIAEnergie version is below 1.8.02.004 and the HandlerPage_KID.ashx handler is accessible to untrusted users.

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 to DIAEnergie version 1.8.02.004 or later. If immediate patching is not feasible, implement input validation and parameterized queries in the affected handler, and restrict network access to the vulnerable endpoint.

Recommended fix High confidence

1.8.02.004

  1. Identify all instances of Delta Electronics DIAEnergie in the environment and note their current versions
  2. Verify the current version is below 1.8.02.004 by checking the application or system information
  3. Back up all configuration files, databases, and critical data before performing any upgrade
  4. Obtain the fixed version 1.8.02.004 from the official Delta Electronics support渠道 or CISA-recommended sources
  5. Test the upgrade in a non-production/staging environment to ensure compatibility with existing systems
  6. Apply the upgrade to production systems following standard change management procedures
  7. After upgrading, verify the version has been correctly updated to 1.8.02.004 or later
  8. Validate that the HandlerPage_KID.ashx endpoint is no longer vulnerable to SQL injection by performing authorized security testing
Caveat Review release notes for version 1.8.02.004 to check for any configuration changes or compatibility considerations with existing systems

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

Fix this in Diaenergie 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 the upgrade done

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-2022-26069 — 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-26069 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