CVE-2022-27175
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 · uneditedDelta Electronics DIAEnergie (All versions prior to 1.8.02.004) has a blind SQL injection vulnerability that exists in GetCalcTagList. 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 confidenceDelta Electronics DIAEnergie contains a blind SQL injection vulnerability in the GetCalcTagList function affecting all versions prior to 1.8.02.004. The flaw allows unauthenticated remote attackers to inject arbitrary SQL queries, potentially leading to database exfiltration, modification, and OS command execution on the host system.
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< 1.8.02.004CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DIAEnergie is installedLocate the DIAEnergie application on the system. Check for installation directories (commonly under C:\Program Files\Delta Electronics\ or C:\Deltaww\) or look for the DIAEnergie service running on the host.Affected if DIAEnergie software is found on the system
-
Determine installed versionOpen the DIAEnergie application or check the Windows Programs and Features list. The version is typically displayed in the application UI, About section, or can be found in the installation directory's version info.Affected if Version displayed is less than 1.8.02.004 or version cannot be determined (treat as potentially vulnerable)
-
Verify vulnerable component presenceCheck if the GetCalcTagList function is accessible. This is a web service endpoint within the DIAEnergie IIS-hosted interface. Confirm the web application is running and the API endpoint exists.Affected if The DIAEnergie web interface is operational and the GetCalcTagList endpoint is accessible
-
Assess network exposureDetermine if the DIAEnergie web interface is accessible from untrusted networks. Check firewall rules and IIS bindings to see if the service is exposed to the internet or untrusted LAN segments.Affected if The DIAEnergie interface is reachable from outside the trusted network without authentication filters
A system is affected if DIAEnergie is installed with a version prior to 1.8.02.004 and the web interface is accessible, since the blind SQL injection in GetCalcTagList can be exploited by unauthenticated remote attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.8.02.004
Upgrade DIAEnergie to version 1.8.02.004 or later to remediate this vulnerability. Until patched, restrict network access to the DIAEnergie interface and monitor for indicators of compromise.
1.8.02.004
- Obtain DIAEnergie version 1.8.02.004 or later from Delta Electronics official channels
- Review all release notes and upgrade documentation provided by Delta Electronics
- Perform a complete backup of the current DIAEnergie configuration, database, and all associated data
- Test the upgrade in a non-production/staging environment to verify functionality
- Deploy the validated upgrade to production systems
- Verify the vulnerability is remediated by confirming the GetCalcTagList endpoint no longer accepts SQL injection payloads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27175 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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