dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-26836

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 HandlerExport.ashx/Calendar. 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 HandlerExport.ashx/Calendar endpoint. Attackers can inject arbitrary SQL queries to retrieve/modify database contents and execute system commands.

MitigationUpgrade to version 1.8.02.004 or later. Additionally, implement parameterized queries and input validation across all handlers to prevent SQL injection.

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 installed DIAEnergie version
    Locate the DIAEnergie installation directory and check the version information file, typically found in the application binaries or configuration files. Common locations include the root installation folder or the bin directory where version.txt, assemblyinfo, or the main executable may contain version metadata.
    Affected if The installed version is lower than 1.8.02.004
  2. Verify the HandlerExport.ashx endpoint exists
    Check for the presence of HandlerExport.ashx in the web application's handlers or scripts directory. This file is typically located in the web root or a handlers subfolder of the DIAEnergie web application.
    Affected if HandlerExport.ashx is present in the web application directory
  3. Confirm the Calendar endpoint is accessible
    Attempt to access the Calendar endpoint through the HandlerExport.ashx handler. This is typically found at a URL path similar to /HandlerExport.ashx/Calendar or within the same URL structure used by the application.
    Affected if The Calendar endpoint responds to HTTP requests (even with an error response indicates the endpoint exists)
  4. Check if the application processes SQL through this endpoint
    Observe the application's behavior when the HandlerExport.ashx/Calendar endpoint is accessed with various input parameters. SQL injection vulnerabilities manifest through unexpected database behavior, error messages, or delayed responses when special SQL characters are submitted.
    Affected if The endpoint accepts user-supplied input and appears to process it as part of SQL queries without proper sanitization

The environment is affected if DIAEnergie version is below 1.8.02.004 AND the HandlerExport.ashx/Calendar endpoint is accessible and processes user input without parameterized queries.

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 version 1.8.02.004 or later. Additionally, implement parameterized queries and input validation across all handlers to prevent SQL injection.

Recommended fix High confidence

1.8.02.004 or later

  1. Upgrade Delta Electronics DIAEnergie to version 1.8.02.004 or later to remediate the SQL injection vulnerability in HandlerExport.ashx/Calendar

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
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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