dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-25980

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 HandlerCommon.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 HandlerCommon.ashx web handler. Attackers can inject arbitrary SQL queries through this endpoint, potentially allowing database content retrieval/modification and OS command execution via the database.

MitigationUpgrade to DIAEnergie version 1.8.02.004 or later. As a temporary measure, implement input validation and consider deploying a WAF in front of the affected web application.

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
    Search for DIAEnergie installation directories or check Windows Programs and Features for Delta Electronics DIAEnergie
    Affected if DIAEnergie is installed on the system
  2. Identify installed version
    Locate version information in the installation directory, typically in an About or Version file, or check the assembly version of the web application binaries
    Affected if The installed version is prior to 1.8.02.004
  3. Verify HandlerCommon.ashx exists
    Check the web application root directory for the presence of HandlerCommon.ashx file
    Affected if The HandlerCommon.ashx file exists in the web root
  4. Assess network accessibility
    Determine if the DIAEnergie web interface is exposed to the network or internet by checking IIS bindings, firewall rules, or attempting to access the web URL
    Affected if The web application is accessible from a network where untrusted users can reach it
  5. Check for application logs
    Review DIAEnergie web application logs for suspicious SQL-like patterns or unusual query parameters directed at HandlerCommon.ashx
    Affected if Evidence of SQL injection attempts or anomalous requests to the handler are found in logs

You are affected if DIAEnergie version is installed and the version is below 1.8.02.004, with the web handler accessible to potential attackers.

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. As a temporary measure, implement input validation and consider deploying a WAF in front of the affected web application.

Recommended fix High confidence

1.8.02.004

  1. Identify the current version of Delta Electronics DIAEnergie currently installed
  2. Backup the DIAEnergie installation and its database before upgrading
  3. Download Delta Electronics DIAEnergie version 1.8.02.004 or later from the official vendor
  4. Install the upgrade following Delta Electronics' standard upgrade procedures
  5. Verify the new version is correctly installed (confirm version 1.8.02.004 or later is running)
  6. Validate that the HandlerCommon.ashx endpoint no longer accepts SQL injection payloads

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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