dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26338

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 HandlerPageP_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 contains a blind SQL injection vulnerability in the HandlerPageP_KID.ashx component. Attackers can inject arbitrary SQL queries without authentication, potentially allowing database content retrieval/modification and OS command execution via the database.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later. Apply input validation and parameterized queries as a defense-in-depth measure.

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 is installed
    Check for the presence of DIAEnergie application directories, typically found in C:\inetpub\wwwroot\DIAEnergie or similar web application paths. Look for the handler file HandlerPageP_KID.ashx in the web root.
    Affected if The application is not found or the version cannot be determined, treat as potentially affected.
  2. Identify installed DIAEnergie version
    Check the version information in the application. The version is often visible in the application title bar when logged in, or check assembly/version files in the installation directory. Also check the About or System Information page within the DIAEnergie web interface if accessible.
    Affected if Version is lower than 1.8.02.004 - the environment is within the affected version range.
  3. Verify HandlerPageP_KID.ashx exists
    Locate the file HandlerPageP_KID.ashx in the web application directory. This file is the vulnerable component. Check if it is present and accessible via the web server.
    Affected if The file exists and the version is below 1.8.02.004, the vulnerability is present.
  4. Check web server exposure
    Confirm the DIAEnergie web interface is accessible over the network. The vulnerability is exploitable without authentication, so if the HandlerPageP_KID.ashx endpoint is reachable, it can be attacked.
    Affected if The web interface and this handler are externally or internally accessible without authentication.

The environment is affected if DIAEnergie is installed with a version lower than 1.8.02.004 and the HandlerPageP_KID.ashx component is present and accessible.

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. Apply input validation and parameterized queries as a defense-in-depth measure.

Recommended fix High confidence

1.8.02.004

  1. Identify all deployments of Delta Electronics DIAEnergie in your environment
  2. Verify the current version of DIAEnergie installed on each system
  3. If the version is prior to 1.8.02.004, plan for upgrade to version 1.8.02.004 or later
  4. Obtain the updated version from Delta Electronics official channels
  5. Test the upgrade in a non-production environment before deploying to production
  6. Schedule maintenance window for the upgrade
  7. Back up current DIAEnergie configuration and database
  8. Install version 1.8.02.004 or latest stable version

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
  • Testing12.0 h
  • Review / QA4.0 h
34.0 hours of engineering $5,880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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