dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-25880

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 HandlerTag_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 HandlerTag_KID.ashx web handler. An unauthenticated attacker can inject arbitrary SQL queries through this endpoint, potentially allowing database content retrieval/modification and OS command execution via database features.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later. As an interim measure, implement web application firewall rules to detect and block SQL injection attempts, and restrict network access to the affected web interface.

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 web application is present
    Identify if the DIAEnergie web interface is accessible on the server by locating web application files or checking for the application's HTTP responses on expected ports (commonly port 80/443 or configured IIS ports)
    Affected if DIAEnergie web application is found running on the system
  2. Identify installed DIAEnergie version
    Locate version information in DIAEnergie installation files, configuration files, or the application's about/page. Compare the discovered version number against the affected range of versions prior to 1.8.02.004
    Affected if Installed version is lower than 1.8.02.004 (for example, 1.8.01.000 or any 1.7.x release)
  3. Locate the HandlerTag_KID.ashx web handler
    Find the HandlerTag_KID.ashx file within the DIAEnergie web application's directory structure, typically in the handlers or bin folder of the web root
    Affected if The HandlerTag_KID.ashx file exists in the web application's deployment
  4. Verify the vulnerable endpoint is exposed
    Attempt to access the HandlerTag_KID.ashx endpoint via HTTP/HTTPS (for example, GET request to /HandlerTag_KID.ashx) and confirm the server responds
    Affected if The endpoint is reachable and responds to requests without authentication

A system is affected if DIAEnergie is installed with a version lower than 1.8.02.004 and the HandlerTag_KID.ashx web handler is accessible on the network.

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 an interim measure, implement web application firewall rules to detect and block SQL injection attempts, and restrict network access to the affected web interface.

Recommended fix High confidence

1.8.02.004

  1. Identify the current installed version of Delta Electronics DIAEnergie
  2. Download DIAEnergie version 1.8.02.004 or later from the official Delta Electronics website or authorized distributor
  3. Review the upgrade documentation provided by Delta Electronics
  4. Perform a full backup of the current DIAEnergie installation, including configuration files and database
  5. Stop all DIAEnergie services before upgrading
  6. Install version 1.8.02.004 following the vendor's installation instructions
  7. Verify the upgrade was successful by checking the installed version number
  8. Restart DIAEnergie services

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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