CVE-2021-32955
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 Version 1.7.5 and prior allows unrestricted file uploads, which may allow an attacker to remotely execute code.
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 1.7.5 and prior contains an unrestricted file upload vulnerability in its web interface. Attackers can upload arbitrary files (such as web shells or executable payloads) to the server without proper validation of file type, content, or destination, enabling remote code execution.
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.7.5CVSS 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.
-
Identify DIAEnergie versionLocate the installed DIAEnergie version number through the application interface (typically found in Help > About, or in installation metadata), or query the system inventory/asset management database for Delta Electronics DIAEnergie software installationsAffected if The installed version is 1.7.5 or any earlier version (1.7.5, 1.7.0, 1.6.x, etc.)
-
Confirm web interface is accessibleVerify that the DIAEnergie web interface port/service is exposed and reachable on the network (typically ports 80/443 or configured HTTP/HTTPS ports)Affected if The web interface is accessible without additional network segmentation or authentication barriers
-
Test file upload functionality exposureIf accessible, examine the web application for file upload endpoints (often found in data import, configuration, or reporting modules). Check whether these endpoints respond without requiring authenticationAffected if File upload functionality in the web interface is reachable without authentication or with weak authentication controls
-
Review upload directory configurationExamine the web server and application configuration to identify where uploaded files are stored. Determine if upload directories are located within web-accessible pathsAffected if Uploaded files can be stored in directories served by the web server, allowing uploaded content to be executed or accessed via HTTP/HTTPS
You are affected if DIAEnergie version 1.7.5 or prior is installed AND the web interface file upload feature is accessible, allowing attackers to place executable content in web-accessible directories.
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.
From vendor dataImplement strict allowlist-based file validation, restrict upload directories to non-executable locations, remove uploaded files from web-accessible paths, and ensure proper authentication/authorization on all file upload endpoints.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32955 — 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-2021-32955 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