dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-43452

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to 1.9.02.001 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
SQL Injection in FtyInfoSetting.aspx in Delta Electronics DIAEnergie versions prior to v1.9.02.001 allows an attacker to inject SQL queries via Network

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 · moderate confidence

SQL injection vulnerability in FtyInfoSetting.aspx of Delta Electronics DIAEnergie (versions prior to v1.9.02.001) allows remote unauthenticated attackers to inject arbitrary SQL queries via network parameters, potentially enabling unauthorized data extraction, modification, or database compromise.

MitigationUpgrade to DIAEnergie v1.9.02.001 or later; if immediate patching is not feasible, implement input validation with parameterized queries on the affected page and restrict network exposure of the management 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.9.02.001

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate DIAEnergie installation directory
    Search for 'DIAEnergie' folder in common web server directories such as C:\Inetpub\wwwroot\, C:\Program Files\Delta Electronics\, or the webroot path used by your IIS server. Check IIS Manager for sites pointing to DIAEnergie.
    Affected if DIAEnergie is found on the system
  2. Identify installed DIAEnergie version
    Locate version information in the installation - check for a version.txt, readme, or the assemblies/DLLs within the DIAEnergie bin folder. The version may also be visible in the page source of any DIAEnergie web page or in the Windows Programs and Features list.
    Affected if Installed version is lower than 1.9.02.001 (e.g., 1.9.01.000, 1.8.x, etc.)
  3. Verify FtyInfoSetting.aspx exists
    Check for the presence of FtyInfoSetting.aspx file in the web application's root or Views folder. On the web server, browse to http(s)://<your-diaenergie-site>/FtyInfoSetting.aspx to confirm the page loads.
    Affected if FtyInfoSetting.aspx file exists and the page is accessible via HTTP/HTTPS
  4. Confirm network exposure of management interface
    Review firewall rules and IIS bindings to determine if the DIAEnergie web interface is exposed to untrusted networks or the public internet. Check whether the site binds to all interfaces (0.0.0.0) or is restricted to internal IPs only.
    Affected if The DIAEnergie web interface (including FtyInfoSetting.aspx) is reachable from untrusted network segments or the internet

You are affected if DIAEnergie versions prior to 1.9.02.001 are installed AND the FtyInfoSetting.aspx page is network-accessible, allowing unauthenticated SQL injection via that endpoint.

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.9.02.001 or later
Fixed in 1.9.02.001
Interim mitigation

Upgrade to DIAEnergie v1.9.02.001 or later; if immediate patching is not feasible, implement input validation with parameterized queries on the affected page and restrict network exposure of the management interface.

Recommended fix High confidence

v1.9.02.001

  1. Identify the current version of Delta Electronics DIAEnergie currently installed
  2. Upgrade DIAEnergie to version v1.9.02.001 or later to remediate the SQL injection vulnerability in FtyInfoSetting.aspx
  3. After upgrading, verify that FtyInfoSetting.aspx is no longer vulnerable to SQL injection
  4. Confirm the new version is running by checking the application version information

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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