dbcve.org
DiaenergieApplication · Deltaww

CVE-2024-43699

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-03
Fix available
A fix is available. Upgrade to after 1.10.01.008 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 is vulnerable to an SQL injection in the script AM_RegReport.aspx. An unauthenticated attacker may be able to exploit this issue to obtain records contained in the targeted product.

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

An unauthenticated SQL injection vulnerability exists in the AM_RegReport.aspx script of Delta Electronics DIAEnergie. Remote attackers can exploit this by injecting malicious SQL queries through the vulnerable endpoint, allowing them to read, modify, or exfiltrate database records without any authentication credentials.

MitigationImmediately apply vendor-supplied patch for DIAEnergie. If unavailable, disable network access to the affected application, implement WAF rules to block SQL injection attack patterns, and consider temporarily isolating the system until remediation is possible.

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.10.01.008

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 DIAEnergie installation
    Locate the DIAEnergie web application directory on the server or identify the web server hosting this application
    Affected if DIAEnergie software is present in the environment
  2. Check installed DIAEnergie version
    Locate version information in application files, assembly metadata, or About/Version pages within the DIAEnergie web interface
    Affected if The installed version is 1.10.01.008 or lower
  3. Verify vulnerable component exists
    Locate the AM_RegReport.aspx file within the web application's directory structure
    Affected if The AM_RegReport.aspx file is present in the deployed web application
  4. Confirm endpoint is network accessible
    Test network connectivity to the AM_RegReport.aspx endpoint from external locations or verify firewall/rules permit access
    Affected if The /DIAEnergie/AM_RegReport.aspx endpoint is reachable over the network without authentication
  5. Review application logs for exploitation attempts
    Search web server access and error logs for unusual SQL syntax, single quotes, UNION statements, or boolean-based payloads sent to AM_RegReport.aspx

A system is affected if DIAEnergie version 1.10.01.008 or lower is installed and the AM_RegReport.aspx endpoint is network-accessible.

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 a release after 1.10.01.008
Interim mitigation

Immediately apply vendor-supplied patch for DIAEnergie. If unavailable, disable network access to the affected application, implement WAF rules to block SQL injection attack patterns, and consider temporarily isolating the system until remediation is possible.

Recommended fix Moderate confidence

Latest stable DIAEnergie release (version > 1.10.01.008)

  1. Identify the current DIAEnergie version installed in your environment
  2. Navigate to Delta Electronics official support portal at www.deltaww.com
  3. Locate DIAEnergie software downloads and release notes
  4. Download and install the latest stable version of DIAEnergie that is newer than 1.10.01.008
  5. Verify the installation was successful and confirm the new version number
  6. Test critical functionalities to ensure the application operates normally
Caveat Review release notes for any configuration or feature changes between your current version and the target version before upgrading

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-2024-43699 — 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-2024-43699 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