CVE-2021-44471
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 · uneditedDIAEnergie Version 1.7.5 and prior is vulnerable to stored cross-site scripting when an unauthenticated user injects arbitrary code into the parameter “name” of the script “DIAE_HandlerAlarmGroup.ashx”.
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 confidenceDIAEnergie Version 1.7.5 and prior contains a stored cross-site scripting vulnerability in the DIAE_HandlerAlarmGroup.ashx handler. An unauthenticated attacker can inject arbitrary JavaScript code into the 'name' parameter, which is then stored and executed when other users access the affected functionality.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 installed DIAEnergie versionLocate the version information in the application's about page, login screen, or header area. Alternatively, check the assembly version of the application binaries in the web application's bin directory.Affected if The displayed or reported version number is 1.7.5 or lower.
-
Verify DIAE_HandlerAlarmGroup.ashx existsCheck the web application's handler or scripts directory for the presence of the DIAE_HandlerAlarmGroup.ashx file. Attempt to access the handler directly via HTTP if the web root is known.Affected if The file exists and responds to HTTP requests.
-
Confirm alarm group management is accessibleLog into the DIAEnergie application and navigate to the alarm group configuration section, typically found in the system settings, alarm configuration, or handler management areas.Affected if The alarm group creation/editing interface is accessible and accepts a 'name' parameter for new groups.
-
Check for existing malicious payloadsReview stored alarm group names in the application's database or configuration files. If database access is available, query the alarm group table for suspicious JavaScript tags in the name field.Affected if Any stored alarm group contains script tags or JavaScript event handlers in its name field.
A user is affected if their DIAEnergie version is 1.7.5 or lower AND the DIAE_HandlerAlarmGroup.ashx handler is present and accessible, allowing stored XSS execution in the 'name' parameter.
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 input validation and context-aware output encoding for the 'name' parameter in DIAE_HandlerAlarmGroup.ashx to neutralize malicious script payloads before storage and before rendering.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44471 — 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-44471 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