CVE-2022-26839
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) is vulnerable to an incorrect default permission in the DIAEnergie application, which may allow an attacker to plant new files (such as DLLs) or replace existing executable files.
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 versions prior to 1.8.02.004 contain incorrect default file system permissions on the application directory, allowing low-privilege attackers to write or replace executable files and DLLs. This enables local privilege escalation through DLL hijacking or executable replacement, achieving code execution in the context of the 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< 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify DIAEnergie installation existsCheck for DIAEnergie installation directory, typically under C:\Program Files\Delta Electronics\ or C:\Program Files (x86)\Delta Electronics\. Use Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DisplayName} to locate the installation path.Affected if DIAEnergie is installed on the system.
-
Determine installed DIAEnergie versionLocate the version information in the installation directory, typically in a file named about.html, version.ini, or in the executable's properties (right-click DIAEnergie.exe -> Properties -> Details). Compare the version number to 1.8.02.004.Affected if The installed version is prior to 1.8.02.004.
-
Inspect file permissions on the DIAEnergie program directoryRight-click the DIAEnergie installation folder, select Properties -> Security tab. Click Advanced. Review the permission entries for users or non-admin groups. Specifically check if Write or Write & Execute permissions are granted toAuthenticated Users, Users, or other low-privilege principals.Affected if Low-privilege users (non-admin) have Write or Write & Execute permissions to the application directory or its subfolders.
-
Check write access to executable filesNavigate to the DIAEnergie bin or root application folder. Right-click on .exe and .dll files, select Properties -> Security. Verify if standard users have Modify or Write permissions on executable or DLL files.Affected if Standard users can modify or overwrite executable (.exe) or dynamic-link library (.dll) files in the installation directory.
-
Identify DLL search order vulnerability potentialReview the application directory for writable DLLs or check if the application loads DLLs from its own directory without strict path verification. Use icacls command: icacls "C:\Path\To\DIAEnergie" to list effective permissions.Affected if The application directory is writable by low-privilege users, enabling DLL hijacking or executable replacement.
A system is affected if DIAEnergie version is below 1.8.02.004 AND the application directory or its executables/DLLs are writable by non-administrative users.
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
Apply vendor-supplied patch (version 1.8.02.004 or later) and audit/remediate file permissions on the DIAEnergie installation directory to enforce least-privilege access controls.
1.8.02.004
- Identify the current DIAEnergie version installed in the environment
- Obtain the fixed version 1.8.02.004 or later from Delta Electronics official sources
- Create a complete backup of the current DIAEnergie installation, including all configuration files, databases, and application data
- Stop the DIAEnergie service or application before upgrading
- Install version 1.8.02.004 following the vendor's standard installation procedures
- After installation, verify that default file permissions are correctly set and restrict unauthorized access
- Restart the DIAEnergie service and validate that the application functions correctly
- Review CISA advisory for any additional configuration recommendations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26839 — 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-26839 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